You the splash get "messed-up" from occasional resave. Don't tell me how, but occasionally the path (which should be relative) becomes absolute
lib_calendar libraries/lib_calendar.livecodescript #which it should be becomes lib_calendary /users/brahma/documents/myapp/libraries/lib_calendar.livecodescript plus you are changing files from time to time, so the stackfiles is obsolete. We fixed this by starting with json files, which then sets the splash stackFiles on stack start up On 3/27/18, 11:13 AM, "use-livecode on behalf of William Prothero via use-livecode" <use-livecode-boun...@lists.runrev.com on behalf of 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 _______________________________________________ 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