Hi,
I just upgraded to spine 4.0 and noticed an "issue" with the latest timeline, caused by this commit:
https://github.com/EsotericSoftware/spine-runtimes/commit/6d9e3e7e19807c016a3480c196027036d291744e#diff-570e7f59fc7aa8b3273a6246d74a970fa077683c55b5f9c8c4279a781bd09752
What I have been doing so far is to use the timeline with spine, then hold the spine animation and then pause the director, while waiting for user input. When the user input is received I resumed the director and continued the timeline animation (including the spine animations). For such moments in the timeline I used some small loop spine animations on the characters on screen. It worked nice until the above commit, where the scene now looks like frozen.
As I understand it, the behavior I was dependent on was a bug and it worked just by accident. For this reason I have created a commit to introduce an option to revert back to way it was working previously.
Please check this commit:
https://github.com/vhristov/spine-runtimes/commit/cd3d8e33599f4c7cd217ee490a0d766b422800a4
If you guys are interested in such a change, I can create a pull request.
P.S. I don't really like the property name I introduced, but so far I was not able to come with a better one...
P.S2 I would prefer to not using a fork and keep everything in sync with what is available in the spine-runtimes repository, so if the change is not acceptable, could you suggest a work around I could use