![]() ![]() ![]() As spine became more mature and powerful, I would expect something similar experience.įrom a programming view, it may be better to version control the export format, so a higher client can export data format for lower version. ![]() I never worrying about my file is losing back-compatibility when upgrading photoshop and AI. Last time I did install java 1.8 was quite some. Upgrade to a patch version (major.minor,patch) then downgrade could be a less restrict process (achievable in editor, without the knowledge of cli). Today I had to downgrade the default java version on Mac because we did start a transition of an existing service. I have just finished my spine work with 3.8, then the client realized the cocos-creator runtime (I guess it's out of your control) is not 3.8 ready because the skin fields breaks, and the compact export issue. ![]() The runtimes are always up to date with all editor features for non-beta releases.I understand it's no good reason to do so, but sometime it just happens. That is a scenario that should be avoided. There is no good reason to do so, except that someone accidentally updated to a new version and did work they want to use with an older runtime. Nate a écrit:The process of loading new data into an old editor is not smooth for a few reasons, but mostly because it is not a workflow that anyone should be using. "skeleton": Downgrade to 3.7 using the skeletonViewer downloaded from. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |