Closed kbilsted closed 3 months ago
Perhaps I've figured it out. I Think the issue revolves around ordering. At the top I redefine the base keys and afterwards I combine them with modifiers. Thus creating some confusing result. Is there a way to get some debug log to be able to track how it evaluates input and sends output. The verbose mode does not print much of this sort of information.
Let me play around with it a bit more before you sink your time into resolving it.
@kbilsted I'm not sure what the Windows equivalent would be but on Linux I can do something like this to debug:
F1 >> $(echo "keypress F1" >> keymapper-debug.log) A
Next release version will contain two features that will greatly help in debugging: https://github.com/houmain/keymapper/issues/91#issuecomment-1946504547.
As an example, the above could be made more convenient:
debug = $(echo "$0" >> keymapper-debug.log)
F1 >> debug["keypress F1"] A
Many thanks @ristomatti . Perhaps we should add it to the readme.. at least until better debug capabilities are implemented
I may quite well have misunderstood something. But here goes
given the following (crazy remap)
When using virtual keys I cannot type digits, instead letters are typed as though i am not holding down
m
if I instead map
m
directlyI can type digits, but after typing the first digit, I'm guessing
key-up M
is also sent since subsequent digits become letters (since it does not register that I have kept holdingm
down). E.g. the sequencedown-M down-Q down-W
types1s
. Now this is useful for one-shot layers... So perhaps a mechanism for both behaviours are needed.I'm not sure if I'm on the path to insanity - I was having fun reducing the number of keys to use on my keyboard ;)