Macro problem

[Zero]

Let's say I want to create a macro for:

Holding shift, keypad 6

This generates P:\[Right] as the trigger, which is the same as if I just pressed the right arrow key. But I already have macros that start with the right arrow key, which makes the new macro have a delay after shift-KP6 is pressed. Is there a way to differentiate the right arrow key from shift-KP6?

Enabling/disabling num lock doesn't help with my problem.

[Garrie]

I believe this is because the IBM keyboard is wired to pass the same signal for both keypresses... the software doesn't even know there is more than one way to make that signal so there is no way to tell the software to do different things for each instance.

[zaimoni]

Originally Posted by Garrie

I believe this is because the IBM keyboard is wired to pass the same signal for both keypresses... the software doesn't even know there is more than one way to make that signal so there is no way to tell the software to do different things for each instance.

No, it's an interpretation issue (if the program works with keycodes rather than interpreted keypresses they can be distinguished.) V uses the usual Windows APIs, so Windows is automatically translating the keycodes to keypresses.

It has been a critical bug to distinguish between right-arrow and shift-KP6 since at least DOS 2.0, so there is no reason to expect Windows to break this anytime soon.