Re: Qustion abut "the stackfiles"

This doesn't matter as the stack files are saved in a place in the standalone where the executable knows where to find them. What the paths are prior to that, relative or absolute, has no effect on the executable. Bob S > On Mar 27, 2018, at 14:52 , Sannyasin Brahmanathaswami via

Re: Qustion abut "the stackfiles"

Do you mean you store the stackfiles in a database, then load the locations with the splash screen? Bill > On Mar 27, 2018, at 2:52 PM, Sannyasin Brahmanathaswami via use-livecode > wrote: > > You the splash get "messed-up" from occasional resave. > > Don't

Re: Qustion abut "the stackfiles"

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

Re: Qustion abut "the stackfiles"

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

Qustion abut "the stackfiles"

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