{#up down left right} sometimes act as numpad arrows?
Opened this issue · 4 comments
Windows 10, Plover 4.0.0.dev11+21.g486a032
I was recently having trouble with some of my keyboard combos not working, and I eventually figured out that it was because my numlock was on. The really weird thing is that it seems to behave differently in different applications: Notepad treats them as arrows even if numlock is on, but they come out as 2468 if I'm trying to launch a program or find a file through the Windows Start Menu, and my Shift+Alt+up/down strokes weren't working in Discord under Chrome.
Turn NumLock on, hit the Windows key to bring up the Start Menu, type one letter (e.g. 'a'). Try to use your up/down arrow key strokes.
Also open up Notepad and mash some text so you have something to move around in, and try using your arrow key strokes while NumLock is on; note that they still work as arrow keys. But if I use the actual numpad on my keyboard, I get numbers.
Searching around for Windows output (keyboard emulation) bugs, there's #1274 but I think it's already fixed in your version.
Then there's incorrect strokes on Plover causes issues on wsl2 with vim · Issue #1410 · openstenoproject/plover (Plover does not send scan code, only key code). Not sure if it's a problem, try applying the patch and see if the problem disappear.
Ah, I didn't think to search on that. And actually I think #1274 is the day after the current release. I'll have a look at both of those, thanks.
Running into this issue, Windows 10 and Plover 4.0.0dev12
With num lock on the Sticky Notes app outputs numbers, and Chrome/Notepad/Discord (desktop app) work fine with the exception of "control shift" selection strokes.
wow I fixed me my problem I've had for ages with abby's left hand modifiers after reading this