Oddity in 'currentCard' function?

[Paul Dupuis]

On 10/26/2023 4:44 AM, Mark Waddingham via use-livecode wrote:
> Basically, its [currentCard] 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'). 

FYI - this is exactly what we use currentCard for in our application - 
change the card that will be displayed when a user shows/opens a stack 
to match a change in user data when the stack is not actually open yet.