Can't call a standalone stack from another standalone stack

[J. Landman Gay]

Francis Nugent Dixon wrote:
> Having problems with a stack call from a SplashStack.
> 
> I have a folder "/Revolution/Standalone" into which I move
> 2 compiled (Intel standalone) stacks (A.app and B.app).
> "A" is supposed to be the SplashStack and sets up a call to
> the other stack (B) in the same folder :
> 
>        go to stack "/Revolution/Standalone/B.app"
> 
> I get an error "stack is corrupted, check for ~ backup file"

If B.app is a compiled standalone, it is no longer a stack. It's an 
application, and you need to use the "launch" command. But is there a 
reason to make it a standalone? Usually only the splash is the 
standalone and all the support files are just stacks.

-- 
Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com