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
-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 a
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
