Josh Goebel

On my list of things to add to the configuration file is `add_device`. https://github.com/joshgoebel/keyszer/issues/19 So we could just do: ``` add_device "Logitech MX Keys" ``` I think having a long...

What is it about the MX that's preventing it from working though? Does it not have capability 1 or does it have a BTN_MOUSE buttons? The criteria is actually pretty...

> BTN_MOUSE translates to code 272 (which is in the list). Yep, that's our problem. My fork already fixes this by changing how "what is a keyboard" is defined... >...

Weird. I have no idea what would be special about Alt-F1 as a combo.

Someone really should make a "record and playback" utill.. record real keystrokes... play them back with a virtual keyboard (on some sort of timer or something)... and observe the behavior......

> Maybe there's some sort of kernel cycle time element that doesn't affect physical keyboards but is messing with the virtual keyboard. Then we might as well throw in the...

> other than nothing being transformed anymore. Right... exactly... you have to test the original non-transformed keystrokes (to get the simplest possible test)... but send thru the virtual keyboard... so...

Next I'd suggest adding some logging to `output#send_event` so you can see the exact key events timestamps... and we'd have to carefully review that log vs the key mapper log......

https://python-evdev.readthedocs.io/en/latest/apidoc.html#evdev.events.InputEvent That's looks like a `PRESS/42` `SYNC/0`... but I'm not sure what the 4 is? What does evtest output say for comparison?

4 4 (EV_MSC MSC_SCAN) the scancode I mentioned. Inputs usually have: - keydown - scancode - keyup With a sync or two thrown in for good measure... you have to...