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 h
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
>
&g
-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"
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
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
