-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows version using numeric keypad with NumLock #81
Comments
I've looked at this previously but didn't get anywhere. I think your investigation notes might be useful so I'll take another look soon. |
This should now be fixed, let me know if you have any further issues. |
OK, well not sure whether I should open a new bug or not regarding this fix. Numlock handling is fixed in the update, but with Numlock turned on, the rest of the keyboard isn't responding. To actually type code, I need to turn Numlock off. Is it worth mentioning that I'm on a desktop computer rather than a laptop? I know some laptops implement Numlock in a way that changes the behaviour of other keys also. |
Someone mentioned this on the syntaxbomb forum. I will make a fix and
upload new .exe's soon
Cheers,
Chris
…On Mon, Feb 3, 2020 at 5:19 PM MrZoolook ***@***.***> wrote:
OK, well not sure whether I should open a new bug or not regarding this
fix.
Numlock handling is fixed in the update, but with Numlock turned on, the
rest of the keyboard isn't responding. To actually type code, I need to
turn Numlock off.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#81?email_source=notifications&email_token=AAF7VYKJ2FHO7OZUOQQI32DRA7AOTA5CNFSM4I5WLLS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKSYGSA#issuecomment-581272392>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAF7VYPKSFFL2S4Q47PCDOTRA7AOTANCNFSM4I5WLLSQ>
.
|
Using the latest Windows version, if I start the program with NumLock turned on, they keypad buttons produce BOTH the number and it's (un-numlocked) action. As in, pressing the '4' button types '4' in the program, but also moves the cursor left, pressing '9' moves the cursor up a page as the 9 is also the PageUp key... etc.
At this point, toggling off NumLock turns the keys into the number only, as if the program is reversing the state of the NumLock function.
HOWEVER, if I start the program with NumLock turned off, the program recognises the state of NumLock, and the keypad behaves as expected, with the NumLock state being recognised properly, and the keys working as expected with or without Numlock.
The text was updated successfully, but these errors were encountered: