Assuming you are doing this so that you can save your stack file, yes. When you make a stack a substack, I do believe it incorporates it all together. However, there is a setting in the standalone builder that avoids this when you build a standalone. Its under the stacks heading, "move substacks into individual stack files."
On Fri, Nov 18, 2011 at 4:36 PM, Bob Sneidar <b...@twft.com> wrote: > Hi all. > > I am a bit confused now. I created a new stack, saved it, made it a > substack of my splash stack. No problemo. I can see the substack on the > hard drive, I can see the substack in the application browser as a substack > of my splash stack. > > BUT THEN... > > I right clicked my splash stack in the application browser, and created a > new substack, named it, saved it, application browser looks peachy, but the > stack file is not visible on the hard drive! Does making a stack a substack > create a COPY of the original stack and imbed it in the main stack, or is > the file hiding somewhere else on my hard drive? If the former, then am I > correct in thinking I do not need the other stack files I CAN see on my > hard drive, because there are now copies of them in the main stack? > > I am soooo confused... > > Bob > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
