optionKeyDown message broken

[Paul Dupuis]

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 are never reported, then 
the bugs will never get fixed.

Sorry, a long frustrating day.


On 4/21/2022 1:04 PM, Craig Newman via use-livecode wrote:
> 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 <use-livecode at lists.runrev.com> wrote:
>>
>> on optionKeyDown pKeyName
>>    if platform() = "MacOS" then
>>      put numToChar(charToNum(pKeyName)-128) into tKey1 -- original sample from Dictionary
>>      put numToCodePoint(codepointToNum(pKeyName)-128) into tKey2 -- trying using non-deprecated functions
>>      answer pKeyName,tKey1,tKey2
>>    else -- windows
>>      answer pKeyName
>>    end if
>> end optionKeyDown
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode