Oddity in 'currentCard' function?

[Mark Wieder]

On 10/26/23 01:44, Mark Waddingham via use-livecode wrote:

> Basically, its main use was for changing card (i.e. as a settable 
> property); rather than finding out what card was current (since that was 
> already catered for via interrogating 'this card of this stack').

So basically to stay out of trouble "currentcard" should be thought of 
as a write-only property?

-- 
  Mark Wieder
  ahsoftware at gmail.com