stackfiles

[Bob Sneidar]

The safe way then to do this would be:

put the stackfiles of stack "test1" into tStackFiles -- or whatever your stack is named
filter lines of tStackFiles with "splash*" -- or whatever your stack short name is
put item 2 of tStackFiles into tFullStackPath
open tFullStackPath

Bob S


> On Aug 9, 2018, at 09:17 , Bob Sneidar via use-livecode <use-livecode at lists.runrev.com> wrote:
> 
> How odd though. The stackfiles is acting like a global property. Imagine I have 2 projects open, each referencing 2 different versions of the same stack in different locations on the disk. Any attempt to open that stack using it's short name might yield the wrong stack. 
> 
> I know you will say: "Well then, don't do that!" But lets say you have a splash stack you use in multiple projects, or a custom dialog stack. You make changes to one stack requiring an update to the other, but that would require that you update ALL the stacks that use the other stack. Rather than do that you might simply save a new version of the splash or dialog stack until you can get around to updating and testing the others. 
> 
> Bob S