Hi Craig, > I cannot save a standalone.
This is true ;-) > In Rev, I have a mainstack "A" with two substacks "B", and "C". I am > trying > to make a standalone of this file, and be able to save stuff on "B". > The file > seems correct, both "B" and "C" give "A" as their mainstack if I ask, > and the > file is definitely "A". > > I make the standalone. I get a file "A". No dialogs, nothing fancy. > > I use the stack "A", as recommended, as an introductory screen and go > right > to "B". I add data to a field on "B". Nothing I do seems to save the > data on > "B". If I close the standalone and then reopen, all my data is lost. I > invoke > all sorts of "save" commands all over the file, especially in "B". > Nada. > > Dammit. Don't make stack B a substack of A because then it is part of the standalone. Make it a separate mainstack and then from stack A go invisible to stack B when your standalone launches. Now you can save stack B. Don't forget to close stack B on exit of stack A. Aloha from Hawaii, Jim Bufalini _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
