Ce site est optimisé pour être consulté depuis un navigateur moderne dans lequel JavaScript est activé.

Confused About the Runtime Documentation

OperationT

Hi All,

Forgive me for my novicehood. I am quite confused about the "Using the Spine Runtimes" documentation (http://esotericsoftware.com/spine-using-runtimes#Animation) because I've come across a few methods that I've used straight out of the documentation, which I realize upon inspecting the source code that it does not match the documentation. For example, I tried using Animation.Apply(skeleton, time, loop) and was faced with an error. Looking at the Animation.cs (from spine-csharp) source code, I realized that Apply consumes 5 parameters (Skeleton skeleton, float lastTime, float time, bool loop, ExposedList<Event> events) instead of 3. lastTime is not documented in the Runtimes Documentation, and after reading the source code documentation, I still don't know what it is. Then I wanted to use Animation.clearAnimation, which I realized is no longer existent at all.

Yet, I've searched many posts in attempt to solve my confusion about the documentation, but unable to find many others in confusion as well.

I hope I don't come across offensive to anyone, as I'm not trying to. I know Nate has worked hard on the Runtimes Documentation from a post I read. I am just looking for some enlightenment. I have some questions that could help me clear some confusion, if anyone could be so kind to answer:

1) Is the "Using the Spine Runtimes" (http://esotericsoftware.com/spine-using-runtimes) documentation indeed outdated? Or am I missing something?

2) In terms of scripting API, are novices expected to get by from just the Runtimes documentation, inspecting the source code, and trial and error? (Asking questions on the forum is great for big questions, but is not time-efficient for many little questions. Mitch's Unity tutorial videos are great, but they don't cover the vast amount of features of the Runtimes (which is understandable and not unexpected).

3) In terms of scripting API, what other sources of information/documentation am I missing, if any?

Thanks for your time 🙂

OperationT

Nate

Sorry, the documentation is somewhat out of date and does not cover some of the newer functionality. The documentation, example code that comes with the runtimes (which is up to date), and the runtime's source code itself are good sources of information.

lastTime is the last time that the animation was applied. This is used by some timelines that want something to occur between lastTime and time. Eg, an attachment change or firing an event. If you pass the same value for both lastTime and time those timelines will not trigger.

events is a list where any events between lastTime and time are added. You can take whatever action you want, or ignore them.

Note that using Animation directly is the lowest level API for applying an animation. AnimationState is implemented on top of Animation and provides more functionality, eg cross fading animations when the animation changes.

OperationT

Thanks for the reply, Nate.

I was initially worried that I would not get anywhere by looking at the source code, but today I did indeed learn more about how to use the Spine API from the source code, albeit very slowly. I suppose I just need to keep pushing until I eventually become adept with Spine!

Mitch

OperationT a écrit
I suppose I just need to keep pushing until I eventually become adept with Spine!

That sounds a lot like me... now look at where I am!