The problem is, then the mainStack cannot be modified, and it needs to be. I set properties in the mainStack. I have settings cards in the mainStack. And besides, I want to eventually have a cool splash screen with a custom shape. It’s called Forms Generator, and I envisioned a generator or maybe something like a grinder with large PDF, Word and Excel icons coming out of it.
Bob S > On Jun 2, 2015, at 16:15 , J. Landman Gay <[email protected]> wrote: > > On 6/2/2015 4:47 PM, Bob Sneidar wrote: >> I was thinking about how to proceed, and I realize that what I need >> to do is have both stacks open, then set the mainstack of each of >> what are now substacks of my app stack, to the splash stack, then set >> the mainstack of my primary app stack to the splash stack. > > I'm not sure there's much point in using the splash method in this case since > it's all just one file anyway and changes can't be saved -- unless, maybe, > you just want a splash image on startup and you don't want that card in the > way later on. But if you don't care about a startup screen, I think I'd just > compile the main stack into the standalone. > > -- > Jacqueline Landman Gay | [email protected] > HyperActive Software | http://www.hyperactivesw.com > > _______________________________________________ > 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
