BoppreH

https://www.codeproject.com/articles/716591/combining-raw-input-and-keyboard-hook-to-selective

The new branch "windows-device-id" now contains a possible solution to this problem. Low Level Keyboard hooks don't include device information. Raw Input Device listeners do, but they don't allow for...

Note to self: https://www.codeproject.com/articles/716591/combining-raw-input-and-keyboard-hook-to-selective (uses DLL, but has interesting ideas on how to pair events) https://github.com/oblitum/Interception http://nate.deepcreek.org.au/dev/keyboardredirector.rails

Yes, I still want the feature and it's still not implemented. It's not my highest priority right now, though.

I still have to work on it to ensure everything is correct, but try removing the lines on _canonial_names (https://github.com/boppreh/keyboard/blob/master/keyboard/_canonical_names.py#L70) that transform "num 5" to simply "5". And you can...

@ornariece any hooks will give you an event object with the scan code. The easiest way is to run "python -m keyboard", press the key and watch what is printed....

Ah, I see the problem. It's a bug that'll be fixing soon, but for now you can workaround by passing a *tuple* instead of a *list*. So if you were...

I agree with it, and I'm working on it on a separate branch (see for example https://github.com/boppreh/keyboard/commit/275b3b466cb71b904aa02c8911e242e5a4b180af ). The challenge is getting all of these types of keys right: -...

Fixing this properly requires a rewrite of the (small) core that handles hotkeys, something that I'm currently working on. Stay tuned!

There are three major complications. 1. Linux events are emitted after-the-fact, so there's nothing we can do to suppress it. Any solution here will require radically changing the way Linux...