send "keyUp" / "rawKeyUp" ?
richmondmathewson at gmail.com
Sun Feb 25 14:50:04 EST 2018
That looks like a good way to start (even though it is the wrong way round).
The next questions (now I'm on a roll, I'll keep rolling) are these:
1. How do I type a rawKey command? I probably cannot.
2. If I have a script that runs type "q" how do I trap therawKeyDown and
the rawKeyUp codes
so I can get them into a field?
In terms of calibration all this will do is nothing as a stack that has
type "q" is a script will
do just that regardless of the end-user's keyboard layout.
I just set my keyboard layout on my ancient iMac (10.7.5) to Bangla
(Bengali), which wouldn't know
a "q" to save its life.
My test stack still typed a "q" into my field.
I wonder what rawKeyDown and rawKeyUp the type command actually sent?
I have a fantasy that goes a bit like this:
select after field "ff"
but LiveCode "doesn't love me" that much.
On 25/2/2018 8:44 pm, Paul Dupuis via use-livecode wrote:
> See the dictionary entry for the "type" command. This sends
> rawKeyUp|rawKeyDown messages
> This might let you construct a stack that "calibrates" (or whatever you
> want to call it) what keys on any keyboard generate what keyDown number
> and what characters
> On 2/25/2018 5:09 AM, Richmond Mathewson via use-livecode wrote:
>> Erm . . .
>> I want to set up a stack that will list an end-user's keyDowns by
>> sending their system
>> a set of rawKeyUps . . .
>> in a button:
>> on mouseUp
>> send "rawKeyDown" to key 113
>> end mouseUp
>> in the cardScript:
>> on rawKeyDown XX
>> get keyUp XX
>> put XX somewhere useful
>> end rawKeyDown
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the Use-livecode