Hello, our team has been using Spine for our Corona app for almost 3 years now. We have some concerns and questions...
Our engineering team, which uses Corona, is currently using Spine Runtime 2.1. Updating past this version, causes issues in our app. I assume this is because Spine hasn't updated the Corona runtimes to v3.0 yet. Therefore, on the runtime side, we're holding off this update until further notice from Esoteric and Spine.
Our art team has been able to continue updating the Spine Editor up to version 3.1.07. Up to this version, we have yet to discover any issues with the fact that we are using different versions of the Runtime and Editor. (On another note, we first noticed issues in incompatibility once our art team began using Editor version 3.2. Therefore, we will likely not update the Editor past version 3.1.07 until the runtimes are compatible, unless you have advice on how we can make that work.)
We recently noticed in https://github.com/EsotericSoftware/spine-runtimes/tree/master/spine-corona the following version information... "spine-corona works with data exported from Spine 2.1.27". I'd assume you would recommend our art team reverting their Spine Editors all the way back to 2.1.27, right? Obviously, they would prefer not to revert back to such an old version of the editor because then they would lose a lot of useful tools and UI changes to which they've become accustomed (for example, filters).
Do you foresee any major issues if our engineering team continues to use the Spine Runtime 2.1 while our art team uses Editor version 3.1.07? If so, how can we mitigate these issues (aside from reverting back to a previous version of Spine Editor, which would be very inconvenient)?
Lastly, is there anything Esoteric can do to help us Corona teams? If you're unable to update our runtimes to v3.0-3.2, can you atleast make a version of the Editor that includes useful updates for our team but is compatible with previous versions of the Spine runtime?
Thank you
