Not to belabor the point, but the stackfiles is a property of a STACK, not a global system property. It would be like setting the foo of stack "test1" to the filename of stack "splash", quitting LC, relaunching LC, opening stack "test1", then expecting to be able to open stack "splash" using it's short name. It's obvious that won't work, so you wouldn't expect the filenames property to make "splash" accessible simply by opening "test1".
But knowledge is power, and as long as we are all aware, it doesn't matter that much to me. Bob S > On Aug 9, 2018, at 11:45 , Richard Gaskin via use-livecode > <use-livecode@lists.runrev.com> wrote: > > Bob Sneidar 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. > > Yes, the stackFiles property is every bit as global as any other use of stack > names. _______________________________________________ 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
