I find it very convenient to use substacks for my main stack module to keep code required by that module together. The mainstack gets a list of the substacks and does a start using for each of them. When i get thousands of lines of code , it is convenient to divide scripts by function, into stack scripts of the substacks. Personally, i love substacks. Bill William Prothero http://ed.earthednet.org
> On Jun 2, 2015, at 9:30 AM, Bob Sneidar <[email protected]> wrote: > > I can see now why people strongly advise NOT to use the substacks feature. It > is none too compatible with standalone building. > > Bob S > > >> On Jun 2, 2015, at 09:19 , Mike Bonner <[email protected]> wrote: >> >> Yep, a substack can't be a mainstack too. >> >> To make this work, its simple enough to just add the stack that has all >> your logic and substacks to the files pane, and add code to your >> splashstack stack that looks for and loads it. (go stack "path/to/stack") >> >> Somewhere around here I have a launcher stack that I have used that I can >> drag and drop stack files on. It adds their path to the list, and from >> that point I can use it to run whatever stack I wish. The same logic >> applies. As long as your splashstack knows where to find a stack, and as >> long as it has the right inclusions for whatever you are doing with your >> stack, it should be able to open it. >> >> On Tue, Jun 2, 2015 at 10:09 AM, Bob Sneidar <[email protected]> >> wrote: >> >>> Hi all. >>> >>> So I am creating a standalone for the first time, and I am trying to use a >>> splash stack. Taking the advice of others I have added a data grid to the >>> splash stack so that the data grid library get added. Now when I attempt to >>> set the mainstack of the actual stack that contains all the business logic, >>> it fails. I think I might know why, but I’ll ask to be sure. >>> >>> The actual application stack has a number of substacks already. I am >>> thinking that a substack cannot itself contain other substacks. If this is >>> true, I will have to break out all of my other stacks as single files, then >>> add them as substacks to the mainstack. >>> >>> If this is true, I can see why new users have problems creating >>> standalones at first. It is a rather convoluted way of going about things. >>> If not, then I am at a loss to know why I cannot set the mainstack property >>> of a given stack. >>> >>> I have also tried using the message box: >>> set the mainStack of stack "Forms Generator" to "Forms Generator Splash” >>> >>> I get: >>> Script compile error: >>> Error description: >>> >>> Bob S >>> >>> >>> _______________________________________________ >>> 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 > > _______________________________________________ > 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
