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 > On Aug 9, 2018, at 09:06 , Bob Sneidar via use-livecode > <use-livecode@lists.runrev.com> wrote: > > Ah! I get it now. > > I tested this. 2 stacks, one with the stackfiles set to a third stack > somewhere on disk. Second one with a button that opens the stack listed in > the stackfiles of the first stack using it's short name. > > With both stacks open, Clicking the button opens the stack listed in the > stackfiles of the first stack. With only the second stack open, I get a > script error. > > So, yes! > > Bob S _______________________________________________ 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
