Probably what will work is to make a stackrunner type of splash stack with any libraries etc included. Then you can have your real stack with its substacks be opened by the splash. As long as the right support stuff is included the splash you can "go stack.." and it should be fine, and the splashstack can handle the saving of changes to your real stack.
On Fri, Nov 18, 2011 at 5:17 PM, Bob Sneidar <b...@twft.com> wrote: > Correction. You cannot go to a card in a new window. The command will > ignore the new window and just go to the card in the existing window. That > would be a nice feature enhancement for having multiple windows open on a > single stack. > > Bob > > > > Thanks Devin I think I understand now. I am going to avoid the whole > problem and go card in new window. > > > > Bob > > > > > > On Nov 18, 2011, at 3:42 PM, Devin Asay wrote: > > > >> Hi Bob, > >> > >> When you turn a mainstack into a substack of another mainstack, that > substack becomes part of the stackfile containing the mainstack. In effect > the stackfile containing the former mainstack is "orphaned". Usually I just > get rid of these orphaned stackfiles to avoid confusion. > >> > >> Bottom line: substacks are part of the same stack file of the mainstack. > >> > >> Hope this it what you were asking. > >> > >> Devin > >> > >> > >> On Nov 18, 2011, at 4:36 PM, Bob Sneidar wrote: > >> > > > > _______________________________________________ > 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
