With NumLock enabled, selecting whole words at a time breaks (i.e. {#Control(Shift(Left))} and {#Control(Shift(Right))})

[aesulus]

Describe the bug

Between plover-4.0.0.dev10 and plover-4.0.0.dev12, {#Control(Shift(Left))} and {#Control(Shift(Right))} functionality seems to have been broken (I have not checked plover-4.0.0.dev11).

To Reproduce

Steps to reproduce the behavior:

1. Define strokes for {#Control(Shift(Left))} and {#Control(Shift(Right))}
2. With NumLock enabled, use those strokes to attempt to select text
3. Cursor is moved across whole words but text is not selected

Expected behavior {#Control(Shift(Left))} and {#Control(Shift(Right))} moves cursor across whole words while selecting text.

Screenshots Testing site used: https://w3c.github.io/uievents/tools/key-event-viewer.html Keystroke output in plover-4.0.0.dev10 (expected)

Keystroke output in plover-4.0.0.dev12 (broken)

Operating system

• OS: Windows 10
• Plover Version: plover-4.0.0.dev12-win64

[aerickt]

I'm not sure if I'm understanding the screenshots, but it seems that NumLock is enabled on both tests. Sometimes having NumLock on can interfere with Plover (see here: https://github.com/openstenoproject/plover/issues/1531). I'd suggest trying the strokes after turning NumLock off.

[aesulus]

Re-ran tests with NumLock off. Output between dev10 and dev12 are now identical.

[aesulus]

updated title and description to include NumLock

[phuertay]

I can confirm this issue still exists in Plover 4.0.0rc2+6.g53c416f, in Windows 11. I'm getting NumpadLeft instead of Left (the arrow).