Oh that is interesting. Still, I can see one use case where separating them is a good thing. There have been times I made a change to one or two substacks, and only needed to replace the versions from the "Standalone" with the new one(s). Also, if a stack is a part of the EXE, aren't the read only? In other words, you cannot save things like properties by saving the stack?
Bob S > On Jun 28, 2019, at 10:34 , J. Landman Gay via use-livecode > <[email protected]> wrote: > > On 6/28/19 10:35 AM, Bob Sneidar via use-livecode wrote: >> I'm under the impression that in a standalone, ALL stacks besides the one in >> the executable are external stacks. That is, the Standalone Builder will >> copy any substacks to a folder as individual stacks. Even in a MacOS >> standalone, the package that is the app can be opened and you will find your >> individual stacks in Resources/_MacOS. > > There is a switch in the Stacks pane of Standalone Settings to control that > behavior. If checked, stacks will be separated out to individual stackfiles. > The default is to leave substacks attached to the mainstack as they are in > the IDE. > > -- > 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
