Each TrackEntry setAnimation
call gives a TrackEntry instance for that animation. Some runtimes do pooling and reuse TrackEntry instances, but that should not usually matter to you. Note you should not keep a TrackEntry reference past when AnimationStateListener dispose
is called for that entry.
Not sure what you mean about the mix duration problem. The API is very flexible to accommodate the many different ways people need to play animations, so sometimes it can be tricky to work out how to get the results you want. We can help if you 1) describe what you want to do and 2) show what you tried and 3) explain what you got versus what you expect (it helps us if you describe those things separately). You can also use Preview and/or Skeleton Viewer to ensure your animations behave as expected, especially when mixing or using multiple tracks. Sometimes it helps to create a simple test case to see behavior without the rest of your app, and as a last resort you can send or post that for us to take a look.