A nasty experience with "the currentcard"

Geoff Canyon gcanyon at gmail.com
Sat Feb 21 09:00:57 CET 2015


Thanks, I figured that out. It was only annoying because I was working on a
stack named with a "rev" prefix, so no error messages were being thrown.

On Sat, Feb 21, 2015 at 1:44 AM, Phil Davis <revdev at pdslabs.net> wrote:

> Try "current card" instead.
>
>    go to current card of stack "x"
>    put the customProperties["myData"] of current card of stack "x" into
>    tMyPropsA
>    etc.
>
> It works.
>
> Phil Davis
>
>
>
> On 2/20/15 9:36 PM, Geoff Canyon wrote:
>
>> It seems currentcard is undocumented. I don't even know where I came up
>> with it. But it works in general:
>>
>>      put the long id of  the currentcard of the topstack
>>
>> works fine in the message box. It also works in the script of a button --
>> generally. As it turns out, the above will give an error *if* the button
>> is
>> in a palette stack, but not if it's in a toplevel stack. (at least in
>> 6.7.1
>> on a mac) I can't really call it a bug since "currentcard" isn't in the
>> dictionary. But it just cost me two hours of my life, so this my primitive
>> yawp of frustration.
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>
>>
> --
> Phil Davis
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>


More information about the use-livecode mailing list