You have to work around with:
Code: Select all
Numpad0::LShift
NumpadIns::LShift
Code: Select all
Numpad0::LShift
NumpadIns::LShift
Code: Select all
a::LShift ; works, because A is remapped too, so once shift converts a UP to A UP, it still gets remapped to LShift UP
Code: Select all
Pause::LCtrl
Code: Select all
While ( 1 ) {
sleep 100
ToolTip % GetKeyState( "Numlock" )
}
Numpad7::NumLock
List of Keys, Mouse Buttons, and Joystick ControlsRemarks wrote:When a script is launched, each remapping is translated into a pair of hotkeys. For example, a script containing a::b actually contains the following two hotkeys instead:
Code: Select all
*a:: SetKeyDelay -1 ; If the destination key is a mouse button, SetMouseDelay is used instead. Send {Blind}{b DownTemp} ; DownTemp is like Down except that other Send commands in the script won't assume "b" should stay down during their Send. return *a up:: SetKeyDelay -1 ; See note below for why press-duration is not specified with either of these SetKeyDelays. Send {Blind}{b Up} return
Now replace a with Numpad0 and b with LShift. What do you expect to happen?Numpad wrote:Due to system behavior, the following keys are identified differently depending on whether NumLock is ON or OFF. If NumLock is OFF but Shift is pressed, the system temporarily releases Shift and acts as though NumLock is ON.
Just reading this part and while I was aware of the behavior, call it a gut feeling, I did some tests, It seems the help is actually back to front here. I believe it should read: "If NumLock is ON but Shift is pressed, the system temporarily releases Shift and acts as though NumLock is OFF." (i.e swapping the on & off around). At least that's how it works for me, When Numlock is OFF, shift acts to shift with the non-numbered numpad keys doing theirs shifted functions.just me wrote:List of Keys, Mouse Buttons, and Joystick ControlsNumpad wrote:Due to system behavior, the following keys are identified differently depending on whether NumLock is ON or OFF. If NumLock is OFF but Shift is pressed, the system temporarily releases Shift and acts as though NumLock is ON.
Not really, it's got nothing to do with ahk, as far as this behaviour is concerned, it's just how the keyboard works when numlock is on. i.e. You can test it in notepad or the quick reply section of this forum, with a few spaces in it so you can see the cursor move. Exit/Suspend all scripts, Put numlock on, push shift and a numpad key, it will do it's numlock off action. AHK is just receiving what is produced.evilC wrote:I assume the crux of this is the use of DownTemp ? I never used it, haven't really wrapped my head around it's implications, so I could not tell you.
Users browsing this forum: mikeyww and 277 guests