Hi guys,
I'm using your latest runtimes (those added 9 days ago) for Starling, but I see that trackEvent is broken and always return 0 as trackIndex.
This is a runtime bug, as everything works fine with runtimes I used before (with same Spine 3.6.5 - the only reason I updated to latest is some meshes & pathes were not processed correctly with previous runtimes)
Example:
I'm having 2 animations (main one for track 1 and background stuff for track 0). But every time event for 'A SCENE 1' fires, it's trackIndex == 0. I switched tracks for animations and see the same trackIndex == 0.
skeleton.state.setAnimationByName(1, "A SCENE 1", true);
skeleton.state.setAnimationByName(0, "background animation", true);
Here is event listener (the same I'm using for almost 2 years with you already - worked perfectly before)
function trackEvent(trackIndex: int, event: Event): void
{
trace('trackIndex: ' + trackIndex + ', animation: ' + skeleton.state.getCurrent(trackIndex).animation.name + ', event: ' + event.data.name);
Mechanics.spineGeneralEvents(event.data.name, event.stringValue, event.intValue, event.floatValue, skeleton.state.getCurrent(trackIndex).animation.name, this, identifier);
}
I can surely write myself a workaround for this, but what I see trackEvent do not return correct trackIndex (or is this outdated function already?)