Re: send "keyUp" / "rawKeyUp" ?

Read again. Got it now. What you effectively want is the (current) foreign keyMapping. This is done by the OS, not gettable by LiveCode AFAIK. Apple even doesn't has a file to check, Linux and Win have. Look what they do: https://wiki.archlinux.org/index.php/Keyboard_configuration_in_console

Re: send "keyUp" / "rawKeyUp" ?

Well . . . That puts "q" into both fields with a US English keyboard layout . . . & ит АЛСО (whoops) it ALSO puts "q" into both fields with a Bulgarian keyboard layout. So "NBG" I'm afraid. Thanks for the suggestion :-) Richmond. P.S. Had to change 'N' to 'M'. On 28/2/2018 11:19 am, hh

Re: send "keyUp" / "rawKeyUp" ?

If I understand correctly what you have in mind then you could try the following. Clicking the button will place one copy of numToCodepoint(M) into both fld 1 and fld 2. Type into the fields as usual, especially you can delete. Typing outside the fields ("blind") will put one copy of space into

Re: send "keyUp" / "rawKeyUp" ?

No, I don't: (Handler: can't find handler) near "rawKeyDown", char 1 Richmond. On 27/2/2018 11:16 pm, Bob Sneidar via use-livecode wrote: Do you mean: send "rawKeyDown" WITH 113? Bob S On Feb 25, 2018, at 02:09 , Richmond Mathewson via use-livecode wrote:

Re: send "keyUp" / "rawKeyUp" ?

Do you mean: send "rawKeyDown" WITH 113? Bob S > On Feb 25, 2018, at 02:09 , Richmond Mathewson via use-livecode > wrote: > > on mouseUp > send "rawKeyDown" to key 113 > end mouseUp > > in the cardScript: > > on rawKeyDown XX > get keyUp XX > put XX

Re: send "keyUp" / "rawKeyUp" ?

It always give a "q" as that is the Unicode name for "q". Richmond. On 26.02.2018 01:55, J. Landman Gay via use-livecode wrote: On 2/25/18 1:57 PM, Richmond Mathewson via use-livecode wrote: I want to send a rawKeyDown signal that fakes typing on the key on my keyboard that has the

Re: send "keyUp" / "rawKeyUp" ?

On 2/25/18 1:57 PM, Richmond Mathewson via use-livecode wrote: I want to send a rawKeyDown signal that fakes typing on the key on my keyboard that has the underlying rawKey code of 113. What does this give you on a non-US keyboard (untested): type numToChar(113) -- Jacqueline Landman Gay

Re: send "keyUp" / "rawKeyUp" ?

11 years ago there was a discussion involving "SendKeys()" http://use-livecode.runrev.narkive.com/9tOIimV9/simulating-keystrokes but I can find no mention of this in the LiveCode documentation. Richmond. On 25/2/2018 10:02 pm, Mike Bonner via use-livecode wrote: If you add rawkeydown

Re: send "keyUp" / "rawKeyUp" ?

If you add rawkeydown handlers to your field, and then use the "type" command to type into them, you'll trap the key code being sent (which will always be the same for q no matter the keyboard) but there is then no relationship to the actual key on the keyboard that I can see. As for your 2 field

Re: send "keyUp" / "rawKeyUp" ?

Here we go again: I reply to my own posting: So: I have 2 fields and a button; the button having this sort of script: on mouseUp put empty into fld "fff" select after fld "fff" type "q" end mouseUp and the cardScript of the stack having this sort of script: on rawKeyDown RD put

Re: send "keyUp" / "rawKeyUp" ?

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

Re: send "keyUp" / "rawKeyUp" ?

Ha, Ha: I do know how my keyboard is laid out. I know, for instance, that if I hit the "q" key I get a raw key code of 113. What I don't know is what "Walid" in Lahore will get when he hits the key on his Mac/Win/Linux keyboard when he hits the key that yields a raw key code of 113 and is in

Re: send "keyUp" / "rawKeyUp" ?

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

Re: send "keyUp" / "rawKeyUp" ?

My apologies. I assumed you knew how the keyboard was laid out on your mac. For other peoples macs, you might read this page. https://stackoverflow.com/questions/21597804/determine-os-x-keyboard-layout-input-source-in-the-terminal-a-script . (goes off to napland) On Sun, Feb 25, 2018 at 11:06

Re: send "keyUp" / "rawKeyUp" ?

That's great, but I'm currently working on a Macintosh. Richmond. On 25/2/2018 7:38 pm, Mike Bonner via use-livecode wrote: Just realized, if all you need to know (On linux) is the basic keyboard information, you can likely do this.. put url "file:/etc/default/keyboard" into and then parse

Re: send "keyUp" / "rawKeyUp" ?

Just realized, if all you need to know (On linux) is the basic keyboard information, you can likely do this.. put url "file:/etc/default/keyboard" into and then parse it. Mine contains KBMODEL="pc105" KBLAYOUT="us" KBVARIANT="" KBOPTIONS="" BACKSPACE="guess" On windows, if the system has

Re: send "keyUp" / "rawKeyUp" ?

Hmm. On linux you might be able to use a shell command to get some info, though I don't know enough about theh output to be much help. the command xkbcom :0 - dumps a truckload of info, might be useful for your task. I'm guessing there is a way to do this on macos too but I don't currently have

Re: send "keyUp" / "rawKeyUp" ?

Either I did not explain things very well or you got hold of the wrong end of the stick (or, most probably a bit of both: probably the latter as a consequence of the former). Imagine, if you will, I need to know what an end-user's standard keyboard layout is. Let's call our theoretical

Re: send "keyUp" / "rawKeyUp" ?

A quick example placed in the card script. local sKeysPushed --keys kept in this variable for the example on rawkeydown pkey if sKeysPushed is empty then put pkey into sKeysPushed else put comma & pkey after sKeysPushed end if -- You would want to remove this block of

send "keyUp" / "rawKeyUp" ?

Erm . . . I want to set up a stack that will list an end-user's keyDowns by sending their system a set of rawKeyUps . . . PseudoCode: 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