Re: Another STANDALONE query, I'm afraid
I now understand how to build a Standalone that saves data in a stack - first make a "stub" stack, and then create your real stack as a substack, and set the standalone options to treat it as a .rev file, so that the standalone user can save to it. My problem is that before I appreciated this, I had created a large stack as a mainstack. Now I want to make it a substack of a new "stub" stack. How do I do this? I hope it's a really simple question that I just can't see the answer to... Make your "Stub" stack as a sub stack of your current main Stack, which I will call "Main" for this example. Go through all the sub-stacks in "Main" and use the popup button in the Basic section of the Stack Inspector to set their mainStack to "Stub". Now set the mainStack of "Main" to "Stub". If "Main" contains a lot of scripts that you want all sub stacks to be able to use, you can copy them all to "Stub", but I prefer to keep the splash screen stack almost empty, so I prefer enabling "Main" as library stack with: start using stack "Main" HTH, Sarah ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Another STANDALONE query, I'm afraid
Specifies which main stack a substack belongs to. set the mainStack of stack to mainStack set the mainStack of this stack to "Central" set the mainStack of stack "Hello" to "Goodbye" HTH TOm On May 4, 2005, at 2:55 PM, John Ridge wrote: I now understand how to build a Standalone that saves data in a stack - first make a "stub" stack, and then create your real stack as a substack, and set the standalone options to treat it as a .rev file, so that the standalone user can save to it. My problem is that before I appreciated this, I had created a large stack as a mainstack. Now I want to make it a substack of a new "stub" stack. How do I do this? I hope it's a really simple question that I just can't see the answer to... -- ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution Thomas J. McGrath III SCS 1000 Killarney Dr. Pittsburgh, PA 15234 412-885-8541 ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Another STANDALONE query, I'm afraid
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 You technically don't need to. Just include the actual stack in the same folder as the "stub" stack, and the standalone "stub" stack should find and open it, just as in the IDE. If you really want to do this anyway, you need to make sure the "real" stack has no substacks of its own (only one layer deep allowed), then simply set its main stack (in the property inspector) to be the stub stack. Save the stub stack. Be weary of unhandled messages from the substack being obtained by the mainstack! On May 4, 2005, at 2:55 PM, John Ridge wrote: I now understand how to build a Standalone that saves data in a stack - first make a "stub" stack, and then create your real stack as a substack, and set the standalone options to treat it as a .rev file, so that the standalone user can save to it. My problem is that before I appreciated this, I had created a large stack as a mainstack. Now I want to make it a substack of a new "stub" stack. How do I do this? I hope it's a really simple question that I just can't see the answer to... -- ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution - --- Frank D. Engel, Jr. <[EMAIL PROTECTED]> $ ln -s /usr/share/kjvbible /usr/manual $ true | cat /usr/manual | grep "John 3:16" John 3:16 For God so loved the world, that he gave his only begotten Son, that whosoever believeth in him should not perish, but have everlasting life. $ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (Darwin) iD8DBQFCeSmq7aqtWrR9cZoRAvaBAJ9crQclFmujD9CndphIxUxq+x6/aACfX61o kZ8EkRvr/NnoigJjlh+ksvA= =m4A1 -END PGP SIGNATURE- ___ $0 Web Hosting with up to 200MB web space, 1000 MB Transfer 10 Personalized POP and Web E-mail Accounts, and much more. Signup at www.doteasy.com ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
RE: Another STANDALONE query, I'm afraid
The answer is in a TAOO folder structure. Spread your stacks in one or many subfolders depending on the context. Your application knows where to search and the rest is go to stack x... The best is to have one engine and many data files you can upgrade without modifying the engine... cheers Xav http://monsieurx.com/taoo > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > John Ridge > Sent: Wednesday, May 04, 2005 20:56 > To: use-revolution@lists.runrev.com > Subject: Another STANDALONE query, I'm afraid > > I now understand how to build a Standalone that saves data in > a stack - first make a "stub" stack, and then create your > real stack as a substack, and set the standalone options to > treat it as a .rev file, so that the standalone user can save to it. > > My problem is that before I appreciated this, I had created a > large stack as a mainstack. Now I want to make it a substack > of a new "stub" stack. > > How do I do this? I hope it's a really simple question that I > just can't see the answer to... > -- > > > ___ > use-revolution mailing list > use-revolution@lists.runrev.com > http://lists.runrev.com/mailman/listinfo/use-revolution > ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
