Closed Aditeya closed 2 years ago
Can confirm, does not work for me too, I will look into it
Issue found, QT does interpret the keys on the numpad as modifiers (for whatever reason) and they therefore get ignored. I will try to find a workaround and push an update.
I just pushed 0.1.26 which should solve this issue, can you confirm it working?
Yes, It works but it seems to accept multiple keys as input on the numpad (with numlock on and off). However, it only uses the last key entered when triggered.
additionally if I make a macro such type 123
from the numpad and the numlock is off then it triggers the alternate keys (ie End
, Down
, Page Down
)
Yes, It works but it seems to accept multiple keys as input on the numpad (with numlock on and off). However, it only uses the last key entered when triggered.
uuh I see, yes that is another bug which is a side effect of this (stupid) workaround for the numpad. will fix that
additionally if I make a macro such type 123 from the numpad and the numlock is off then it triggers the alternate keys (ie End, Down, Page Down)
That is something I cannot influence or change. Keyboard Center does simulate the keypress as if you would physically press it. So it will behave depending on the state of the numlock the moment the macro is executed.
oops closed by mistake
pushed fix for the multiple keys issue as 0.1.27
the second issue is a wontfix, since I am simulating the physical button press and therefore cannot take the state of numlock into account (in fact the OS does that when handling the keypress).
Yep, it works as expected. Also to detect numlock state, you could use numlockx
. However, it wouldn't work on wayland since it is a X11 program.
ok thanks for the feedback, will close this issue then.
Also to detect numlock state, you could use numlockx. However, it wouldn't work on wayland since it is a X11 program.
Yes I know that there are multiple options to implement that, but I want to stay as desktop environment agnostic as possible, which is why I use the uinput and udev kernel modules instead of any X11 or Wayland based solution.
It would be possible to make the application aware of the numlock state, but that would add complexity that I frankly do not want to maintain :/.
If I try to add a key, from the numpad, on to the macro input box, nothing happens. It accepts
NumLock
but won't accept any keys from the numpad. I'm running this on Arch Linux with the bspwm TWM.