Bob ...while I tested the previous solution ...I have not yet gone through the implementation of it for real ........ but I think I will do what you suggest. It makes sense ...it should work as long as no handlers are running on the main stack, I can replace its script. Thanks.
On Tue, Jan 22, 2019 at 12:54 PM Bob Sneidar via use-livecode < [email protected]> wrote: > You do not need to make the splash stack the mainstack. Just include the > actual mainstack in the Stack Files of the splash screen stack, and when > have code in the splash screen stack that opens the main stack. Then you > can still keep your stack/substack structure of your project. > > Bob S > > > > On Jan 20, 2019, at 18:05 , Geoff Canyon via use-livecode < > [email protected]> wrote: > > > > Sure, just create the stack you want to use as the splash screen, and > then > > set the mainstack of the current mainstack to the splash screen stack. I > > think this will fail if the mainstack has substacks of its own. So first > > change the substacks, then the mainstack. And if you are depending on the > > substacks being able to reference handlers/functions in the (current) > > mainstack, either move the handlers and functions to the new mainstack, > or > > convert to a behavior stack and use that for everything. > > > > gc > > > _______________________________________________ > use-livecode mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
