2.0 - Simulated keystroke for {LEFT} broken in during mode

[evilc]

In 2.0, setting a button to "Simulated Keystrokes" and "During" for the arrow keys gives the number on the numberpad for that arrow.
So {LEFT} gives 4, {RIGHT} gives 6 etc.

If you set the remapping to "Pressed", the remap functions normally.

[phil]

What is the state of the "Numlock" option in general settings and does it make any difference?
Also does the numlock key make any difference?
Thanks,
Phil

[evilc]

Aha!
If numlock is on (Light lit) - I get 4. If it is off, I get left.

[phil]

There is a setting in general settings to "Ignore" numlock state. Have you tried ticking that?
It is possible the the "during" mode is not respecting that setting while pressed etc. is. It would be good to know because it will make the fix (if required) more obvious.

Thanks,
Phil

[evilc]

No I didn't, as it only manifests in "during" mode, i guessed it was a bug.

[phil]

I just edited my previous post but incase you missed that....
It may still be a bug, that setting may be ignored in during mode. If you could check it would be nice to know.
Thanks
Phil

[evilc]

OK, confirmed - the option has no effect

[phil]

Thanks, its a proper bug then I'll add it to the list

[evilc]

Not sure I agree with the coding of this even when it is "working".
Surely sending {Left} should be the same no matter what the numlock status.

Surely there should be a key like {KP4} ("Keypad 4") that could be different things (ie Left or 4) depending on numlock state.
I say this because the arrow keys to the left of the keypad function no matter the state of numlock.

[evilc]

oops, there IS a {NUM4}
However, it works the opposite way !?!?

So Sending {Num4} ignores numlock state
But sending {Left} does not.

Illogical, this should be the other way around.

[phil]

Ahhh ok I think I remember... Someone wanted to use the num keys and it was sending arrows... so I added the setting for the keys, but I think the arrows should also honour the same setting. eg. always send the left/right what ever the numlock state.

Thanks
Phil

[evilc]

but I think the arrows should also honour the same setting. eg. always send the left/right what ever the numlock state.

I am not sure I am getting you here - Do you mean "I agree, this should be changed", or "This is intentional"?

From what you are saying, the user's requirements would still be met by using the "Ignore numlock" setting and changing things to how I am proposing.

[evilc]

Mind you, thinking about it -the "Ignore numlock" option probably needs to be expanded.

I think you would want "Ignore numlock - process as if always ON", and "Ignore numlock - process as if always OFF"

[evilc]

Sorry to keep posting, but thinking about it there is probably a simpler solution.

You need 3 lots of tags

One set that adheres to Numlock state.
{KP1}, {KP2}, {KPIns} etc

Two sets that always ignore numlock state:
{NUM1} to {NUM9} - The Numlock ON versions
and
{NUMEnd}, {NUMDown}, {NUmPgDn}, [...] - The Numlock OFF versions.

Then you wouldn't need the "Ignore numlock" option and you could always specify exactly what you want.

[phil]

I think Ive fixed this in v2.1 Beta2 (details here).

I have not gone down the route of all the extra options, I have just fixed left,right,up,down,ins,del,home,end,pgup & pgdn which were all broken in during mode (using the numpad versions of these keys instead of the "fixed" extended keys (to the left of the numpad on most keyboards).

Give it a try and let me know if its good for you.

Thanks,
Phil