Sendkeys syntax for arrow keys

[wraith]

I'm trying to map the Arrow keys (not the arrow keys on the number pad).
Example: I tried using macro = {LEFT} and il-2 maps it as Numpad 4.

What is the corrent sendkeys for the arrow keys?

[zorlac]

ah yes, the non-alpha-numeric keys... what a pain they have been :)

macro = predef:LEFT
or
macro = predef:RIGHT
or
macro = predef:UP
or
macro = predef:DOWN

These macros will send one single key event when triggered. If you want to be able to press and hold a button, and have the arrow keys held down while doing so, then let me know and i`ll explain how to do that too.

FYI - there is a brief description on predef and rawkeys in the docs folder, the file you want to look at is called predef-and-rawkey-reference.html.

[wraith]

Thank zorlac.
How would it work if i wanted to make a combination? ie. Shift-Up Arrow or Ctrl-Up Arrow...etc.

[zorlac]

OK, quick overview of how key events work

Each key event comprises of a key down event and a key up event. This is how keyboards work... they register a down event when the key is pressed, and an up event when released. The system takes these events and stores their status away somewhere, so it can be interogated by applications.

In the previous example for the arrow keys, they were simple:

predef:LEFT, KEYDOWN
predef:LEFT, KEYUP

(if you dont define a KEYDOWN or KEYUP events, TB assumes you want a single press and sends a DOWN then an UP event).

If you want to combine keys, you have to start breaking it down into exactly what it is the keys should be doing. You wanted to know how the macros would look for Shift-Up, so lets look at that.

predef:SHIFT, KEYDOWN
predef:UP, KEYDOWN
predef:UP, KEYUP
predef:SHIFT, KEYUP

Read that carefully, and understand what it is doing. Its registering a SHIFT KEYDOWN event, then a UP KEYDOWN event, so the system will see both these keys as selected. They you have to send the KEYUP events to set it all back to normal, and its best practise to send the KEYUP events in the reverse order that they were set as KEYDOWN.

BEWARE - you *REALLY* have to be careful when constructing predef macros... ensure that for every KEYDOWN event, you have a corresponding KEYUP event for that same key, or the keyboard status will be left in an unknown and unpredictable state, with keys being left in the DOWN state... it can get really nasty

Does that explain it a bit clearer?

[wraith]

I get it lnow zorlac. I've never coded keystrokes before so it's a bit of a primer for me.
I'll try it later tonight and report back if I have any issues.

Thanks again for your help.

[zorlac]

It was all new to me too when I started, and I had to find out the hard way