weird standalone save behavior
Richard Lague
laguer at ucs.orst.edu
Mon Apr 3 02:00:19 EDT 2006
On Apr 1, 2006, at 12:00 PM, Richard Gaskin wrote:
> Richard Lague wrote:
>> In an effort to figure out what is going on I have been using the
>> following script for saving:
>> ON mouseUp
>> save this stack
>> IF the result is not empty THEN
>> put the result into resultVar
>> answer resultVar
>> ELSE
>> answer "save confirmed"
>> END IF
>> END mouseUp
>> When I can not save data I always get the same result: “Can’t
>> open stack file”.
>
> Are you sure that in the context it's being called "this stack"
> refers to the stack you want and not the standalone?
The script is in a button on the sub-stack. I have been testing this
with a very simple standalone -- a one-card main stack/application
that has one sub-stack. The sub-stack is also only one card that has
a "save" button and a text field.
>
>
> --
> Richard Gaskin
> Managing Editor, revJournal
> _______________________________________________________
> Rev tips, tutorials and more: http://www.revJournal.com
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
More information about the use-livecode
mailing list