Paul. The construction "answer this card of stack “X” does not work if you are not on stack “X”:
answer the currentCard of stack “X” —works answer the name of this card of stack “X —works answer this card of stack “X”—Nope Craig > On Oct 25, 2023, at 8:57 AM, Paul Dupuis via use-livecode > <use-livecode@lists.runrev.com> wrote: > > On 10/25/2023 12:34 AM, Mark Waddingham via use-livecode wrote: >> >> If you want to do stuff with the current card of a stack, then don't use the >> currentCard property - 'this card of stack ...' *is* a chunk reference and >> thus it doesn't care whether the card has a name or not. >> > > Okay, I get that <object> id <number> is a legacy return value when there is > no name. > > I'd just like to confirm that: > > this card of stack "X" > and > the currentCard of stack "X" > > refer to the same card, even if in different ways (actual object reference vs > short name)? > > If so, I will switch to using "this card of stack". I had thought that the > 'this card' was always the card in the object hierarchy of the object the > script was running in and had forgotten that you could say 'this card of > stack ...' to reference the active card in another stack. > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
