Stand-alone issues: lost images and go to (sub) stack scripts fail

[J. Landman Gay]

On 3/21/11 6:10 PM, Keith Clarke wrote:
> Hi folks, I need some help struggling with deploying my first
> multi-stack stand-alone. Images in the main stack and sub-stack
> (within the same folder as the .rev file) are greyed-out on both Mac
> and web deployments. On the web deployment none of the button or link
> scripts that use 'go to stack' to access sub-stacks work. Any advice
> on where to start trouble-shooting greatly appreciated.

It's a path problem. If your stacks are separate files on disk, they 
aren't "substacks", they are just document stacks like any other app's 
documents. You'll need to provide a full file path to open them.

Another way to do it is to set the stackfiles property of your 
mainstack. Use relative paths when you set that up. If your stackfiles 
point to the proper locations relative to the main stack then you can 
use short stack names to refer to the document stacks.

If during development you really are using substacks (stacks embedded in 
the same file on disk) then just leave them that way when you build. 
Don't set the option that moves substacks into separate files. That will 
solve the problem with referencing stacks.

If your images are being loaded from disk, try setting the "Copy 
Referenced Files" checkbox in the "Copy Files" pane of the standalone 
builder. That should set up the file references for your images.

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