paulswartz
Numlock prevents key registration
With numlock disabled, I can move windows around as expected. When I turn numlock on, nothing happens.
If the terminal running gnome-shell-grid.py has focus, the numbers from the keypad get entered in the terminal. If another window has focus, the terminal doesn't output anything.
The NumLock get does basically what it says; it locks the keys so that they're used as numbers rather than keys. I can see a couple possible changes:
- put a message in the console, either at startup or every time, when NumLock is on
- add a commandline option to ignore NumLock, and bind to the keys anyways. This might interfere with the regular numbers, though.
The first change seems unambiguously good, so I'll make that. I'll think about the other one.
Thanks for implementing the warning message.
I think the command line option to ignore NumLock would be great. I'm on my laptop right now and my "keypad" is integrated into the regular keyboard. The only way I can activate the keypad is by turning on NumLock. I wouldn't worry about locking the keys as numbers absolutely because it should only register when C-M-* is pressed, where * is a keypad number. Without the C-M, the keys will still produce numbers.
Now, I'm pretty much making this up out of thin air. I'm not sure what difficulties, if any, are present in detecting a number input as a keypad hit.
If you don't have a separate numpad, can you use the C-M-S keys instead? I implemented them so I could use gnome-shell-grid from my laptop keyboard.
I have C-M-S [h, j, k, l] bound for moving windows between workspaces. Seeing as this is just a very particular use case, it's probably not worthy to support.