Re: plugin stack automatically saving in new file format
Excellent. Thank you, and thanks to Mike as well. I’ll implement that in my code. > On Dec 18, 2014, at 2:39 PM, Klaus major-k wrote: > > Hi Chris, > >> Am 18.12.2014 um 21:30 schrieb Chris Sheffield : >> >> I have a custom plugin stack that I use to quickly open frequently used >> stacks. It has a “save this stack” command in its closeStack handler. If I’m >> working in LC 7.0+ the stack is saving with the new file format, and >> therefore won’t open in pre-7.0 versions of LiveCode. I though once a stack >> was saved in a legacy format, it would stay in that format. Is that not the >> case? Is there any way to prevent the file format change when saving a stack? > > I think "the stackfileversion" global property will help here! > > Do something like this: > ... > ## Save current stackfileversion value: > put the stackfileversion into tOldSFV > > ## See dictionary for other possible values > set the stackfileversion to "5.5" > save this stack > > ## Restore old value: > set the stackfileversion to tOldSFV > ... > >> Thanks, >> Chris > > Best > > Klaus > > -- > Klaus Major > http://www.major-k.de > kl...@major-k.de > > > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: plugin stack automatically saving in new file format
Hi Chris, > Am 18.12.2014 um 21:30 schrieb Chris Sheffield : > > I have a custom plugin stack that I use to quickly open frequently used > stacks. It has a “save this stack” command in its closeStack handler. If I’m > working in LC 7.0+ the stack is saving with the new file format, and > therefore won’t open in pre-7.0 versions of LiveCode. I though once a stack > was saved in a legacy format, it would stay in that format. Is that not the > case? Is there any way to prevent the file format change when saving a stack? I think "the stackfileversion" global property will help here! Do something like this: ... ## Save current stackfileversion value: put the stackfileversion into tOldSFV ## See dictionary for other possible values set the stackfileversion to "5.5" save this stack ## Restore old value: set the stackfileversion to tOldSFV ... > Thanks, > Chris Best Klaus -- Klaus Major http://www.major-k.de kl...@major-k.de ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: plugin stack automatically saving in new file format
There is a preference that says to preserve stack file format, but i'm not sure if it applies when a stack is saving itself. (seems like it should, but hey, you never know). The best way to avoid this is to set the stackfileversion to what you want, right before the save. Theres an example of this in the dictionary entry. Basically, it saves the current stackfileversion to a variable, sets the stackfileversion to the version you wish to save as, saves the stack, then resets the stackfileversion. On Thu, Dec 18, 2014 at 1:30 PM, Chris Sheffield wrote: > > I have a custom plugin stack that I use to quickly open frequently used > stacks. It has a “save this stack” command in its closeStack handler. If > I’m working in LC 7.0+ the stack is saving with the new file format, and > therefore won’t open in pre-7.0 versions of LiveCode. I though once a stack > was saved in a legacy format, it would stay in that format. Is that not the > case? Is there any way to prevent the file format change when saving a > stack? > > Thanks, > Chris > > > -- > Chris Sheffield > Read Naturally, Inc. > www.readnaturally.com > > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
plugin stack automatically saving in new file format
I have a custom plugin stack that I use to quickly open frequently used stacks. It has a “save this stack” command in its closeStack handler. If I’m working in LC 7.0+ the stack is saving with the new file format, and therefore won’t open in pre-7.0 versions of LiveCode. I though once a stack was saved in a legacy format, it would stay in that format. Is that not the case? Is there any way to prevent the file format change when saving a stack? Thanks, Chris -- Chris Sheffield Read Naturally, Inc. www.readnaturally.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
