Sadly event.code will not work in this instance because alternative layouts such as Dvorak misreport their key. For example in Dvorak, pushing x will result in KeyB while pushing b will result in KeyB also.

I'll close this PR as it will introduce new bugs which we've already fixed prior. I welcome new ideas to fix this though!

Em, is that really problem? It's their implementation problem's.

I am not referring to an implementation, but the underlying mechanics of event.code - it specifies the keyboard character which means it does not support switching layouts. The same is true of any alternate layout, not just specific ones. We made a switch from event.code to event.key to solve precisely this bug.

btw .code is newer than key, so, i think key gonna be deprecated soon.

Maybe we should just make detector?

Happy to explore ideas. I'm not sure how a detector could be made. You could compare code and key, and if there's a discrepency, then... I'm not sure how you'd resolve that?

Yep, as u suggested. Just try to emulate key press, and check what's going on.

https://github.com/ahtcx/layoutline
btw it's also just piece of shit, u r right.