Ah, thx richard, but didn't know it was only the main, but it makes sense. So, if you want to save a substack as a separate stack file, you'd have to a) set its mainstack property to itself, and b) set the path and filename you wish to save it to before you save it, otherwise the "save as" dialog will always pop up.
If you just want to save the mainstack (which wouldn't work in a standalone anyway unless using the splashstack method) You'd want to make sure you were actually saving the mainstack, which would of course save its substacks. And as richard said, any newly created or downloaded mainstacks won't have the filename set, so you'd have to do that in code before calling save if you don't want it to pop up the dialog. On Fri, Feb 6, 2015 at 6:40 PM, Richard Gaskin <[email protected]> wrote: > Bob Sneidar wrote: > > > filename does not seem to be a property of a stack. > > The filename is a property of mainstacks. For substacks use "the > effective filename". > > For stacks that have been newly created, or downloaded over the Web, the > filename will be empty. > > -- > Richard Gaskin > Fourth World Systems > Software Design and Development for the Desktop, Mobile, and the Web > ____________________________________________________________________ > [email protected] http://www.FourthWorld.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
