This is the prescribed way to do this in a splash stack scenario. The Splash Stack becomes your executable, and all the other stacks, including the *actual* application stack end up in the right place as editable stacks. (The Executable stack is not editable so you cannot set properties that stick from session to session, or save the stacks state.)
Bob S > On Mar 27, 2018, at 14:13 , William Prothero via use-livecode > <use-livecode@lists.runrev.com> wrote: > > Folks: > I’m setting up an application with a splash stack and lots of other stacks > and libraries that are loaded by the splash stack. I am using “the > stackfiles” of the splash stack to get the relative paths of the various > stacks in the resources folder. I’m on LC 9.0.0(rc2), on Mac OS 10.12.3 > > What I’m wondering is if there are any “gotchas” with using this method to > get the relative paths to the various resource stacks. It seems like this may > be the easiest way to adjust paths for the various deployment targets. > > Best, > Bill > > William A. Prothero _______________________________________________ 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
