standalone loading script-only stacks

Matt Maier blueback09 at
Fri Feb 19 16:50:46 EST 2016

The handlers are incomplete because I only pasted in the parts that led to
each other. The rest of the handlers would be long and irrelevant.

It looks like the problem is caused by the ask and/or answer dialog. The
first few lines where properties of those stacks are set cause the setup
handler to error out. Other functions that depend on ask/answer aren't
working correctly either.

So I got 90% of the app to run by commenting out the lines setting popup
properties in the setup. I got the answer popup to appear in the
stand-alone by switching a button in the stand-alone application settings.
The ask popup is still missing in action.

Any ideas how to get those into the stand-alone?
On Feb 18, 2016 10:02 PM, "J. Landman Gay" <jacque at> wrote:

> On 2/18/2016 10:58 PM, Matt Maier wrote:
>> The log works just fine in the IDE, but it doesn't start in the
>> least not right away. If I start poking at the controls
>> the
>> log might spontaneously start working for some reason.
> The quickModeSetup handler has no "end" statement so it may not be
> compiling correctly. I'm guessing that poking other controls may call
> devLog (which does have the right structure) so that's why it works later.
> I'm not sure why it would work in the IDE though, I'd have thought it
> wouldn't.
> The setupAsOf3FEB2016 handler also has no "end" statement.
>> The real problem here is that the rest of this startup process is supposed
>> to create a bunch of graph objects, but they're not appearing in the
>> standalone.
> The preOpenStack handler is using the path to the mainstack as the basis
> for determining where the other stacks are located:
>    set the defaultStack to "HowstrBeta"
>>    set the itemDelimiter to "/"
>>    get the effective fileName of this stack
>>    set the defaultFolder to item 1 to -2 of it
> Replace these four lines with:
>    set the defaultfolder to specialFolderPath("resources")
> Depending on the OS, standalone resources are copied to different
> locations outside the mainstack folder, and the original handler won't find
> them. You can always get their location with specialFolderPath("resources")
> which will always point to the right place. In the IDE,
> specialFolderPath("resources") points to the folder that contains the
> mainstack, which makes things easy; store the stacks in the same folder
> with the mainstack as you do now, and use specialFolderPath to find the
> stacks during both development and in a standalone.
> --
> Jacqueline Landman Gay         |     jacque at
> HyperActive Software           |
> _______________________________________________
> use-livecode mailing list
> use-livecode at
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:

More information about the use-livecode mailing list