FYI for anyone who is interested:
I submitted a bug report for the broken state of the optionKeyDown
message. See https://quality.livecode.com/show_bug.cgi?id=23688
Please follow if you are interested in seeing this fixed.
___
use-livecode mailing
On 4/21/2022 3:27 PM, J. Landman Gay via use-livecode wrote:
On 4/21/22 10:55 AM, Paul Dupuis via use-livecode wrote:
In a new stack, place the following in the card script:
on optionKeyDown pKeyName
if platform() = "MacOS" then
put numToChar(charToNum(pKeyName)-128) into tKey1 -- origi
On 4/21/22 10:55 AM, Paul Dupuis via use-livecode wrote:
In a new stack, place the following in the card script:
on optionKeyDown pKeyName
if platform() = "MacOS" then
put numToChar(charToNum(pKeyName)-128) into tKey1 -- original sample from
Dictionary
put numToCodePoint(codepointT
Yes, there are work-arounds. My post was about confirming the bug so I
can report it to Livecode.
In this case, we have a shipping application in which the optionKeyDown
handler USED to work that now a customer has (correctly) reported it
broken.
If everyone just codes work-arounds and bugs
Have not played with your handler, but why not just:
on rawKeyDown tKey
if the optionkey is down then answer numToChar(tkey)
end rawKeyDown
Craig
> On Apr 21, 2022, at 11:55 AM, Paul Dupuis via use-livecode
> wrote:
>
> on optionKeyDown pKeyName
> if platform() = "MacOS" then
> put n
