Re: Oddity in 'currentCard' function?

2023-10-26 Thread J. Landman Gay via use-livecode
On 10/26/23 2:26 PM, J. Landman Gay via use-livecode wrote: It can be read if you supply syntax that requests a legal value; i.e.:   the name of the currentCard of stack X   the loc of the currentCard of stack X   the backColor of the currentCard of stack X Oops. That's wrong. It errors.

Re: Oddity in 'currentCard' function?

2023-10-26 Thread J. Landman Gay via use-livecode
On 10/26/23 11:17 AM, Mark Wieder via use-livecode wrote: So basically to stay out of trouble "currentcard" should be thought of as a write-only property? It can be read if you supply syntax that requests a legal value; i.e.: the name of the currentCard of stack X the loc of the currentCa

Re: some mobilecontrolprops do not work on Android?

2023-10-26 Thread J. Landman Gay via use-livecode
The backgroundColor and alpha settings might be a dictionary error. The opaque setting says it is available only for iOS. I think the appearance of mobile players is set directly by the OS now, so the color and transparency may not be available on Android. On 10/26/23 9:56 AM, Klaus major-k v

Re: Oddity in 'currentCard' function?

2023-10-26 Thread Mark Wieder via use-livecode
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 t

some mobilecontrolprops do not work on Android?

2023-10-26 Thread Klaus major-k via use-livecode
Hi friends, I (now successfully :) create a player for MP3 playback, however some properties do not seem to work on Android, although the Dictionary states otherwise!? -- mobilecontrolCreate "player", "mplayer" mobileControlSet "mplayer", "visible", TR

Re: Oddity in 'currentCard' function?

2023-10-26 Thread Paul Dupuis via use-livecode
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

Re: Oddity in 'currentCard' function?

2023-10-26 Thread Mark Waddingham via use-livecode
On 2023-10-25 13:57, Paul Dupuis via use-livecode 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

Re: Oddity in 'currentCard' function?

2023-10-26 Thread Mark Waddingham via use-livecode
On 2023-10-25 15:41, Craig Newman via use-livecode wrote: 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 'this