@Klaus, no, your not overlooking it at all, there is no example in dictionary of it's use. I was just going to brute force use anything I could think of and hopefully tumble onto it, but it appears "stack version" isn't backwards compatible either ~!
jacque wrote: ↑
Mon Jun 17, 2019 6:37 pm
Every now and then the format of LC's stack binary has to change to accommodate new features. This has happened maybe 4 or 5 times over the years.
OH I know all about that heh, as many versions I use frequently have had many format changes over the years, but this is a first time challenge for me, so I'm wondering specifically how others deal with it, after I tried (and failed) to figure it out on my own.
The stack has a 'save this stack' line in it's "on closeStack" handler. The stack is also a plugin. Now, I know I can stick this stack into the main plugin folder in the IDE folders, which is where it was originally, and that is fine for me. In fact, in Mc, there is no other option.
However, if someone comes along in the future and downloads this plugin, and decides they like it, as the engine changes format over the ensuing years, it is probably unlikely they will want to move it from IDE to IDE. However, they may want to use it in any one of the versions they use, no matter how old it is.
I realize I am an oddball way outside edge special snowflake test case, but I'm sure there are people using say, IDE v7 while also using say, 9, and the two formats aren't compatible. So if they open it in the 9.x IDE, I wouldn't like to see them open the 7.x IDE and have it say it can't read the stack.
I know lots write plugins that span versions, so naturally I am curious how it is normally handled.