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

[Keith Clarke]

Hi Jaque,
Thanks for response. I'm not sure that paths were the problem, though using your suggestions I did discover that the LiveCode standalone builder doesn't like files on DropBox! Anyway, the image problem is now solved but I'm not being so lucky with moving between substacks in the revlet...

> 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.
Unfortunately, copying reference files didn't work nor did adding the specific image file. So, I imported the image as a control into the .livecode file - that worked OK.

> 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.
All the substacks are in the one, single .livecode file on disk. They all appear in the 'Stacks in the referenced stack file:' dialogue in the Stacks pane of the standalone settings utility and the 'Move substacks into individual stackfiles' option is set to false. I can't tell whether the standalone builder has generated the substacks and the scripts are failing or vice versa. The substacks are currently single card stacks and the scripts are very simple, for example:

on mouseUp
   go to stack "Editor"
end mouseUp 

Do I have to be careful with the syntax for moving between stacks - or the mode of the target stack - when deploying into a revlet?
Best,
Keith..