jonasBoss
jonasBoss
the wheel macro was changed to support high resolution scrolling. you need to change the speed i.e. `wheel(up,120)`. Or you can use the event macro instead `event(2, REL_WHEEL, 1)` or...
> 2. If a button on your device doesn't show up in the GUI, verify that the button is reporting an event via `sudo evtest`. If not, input-remapper won't be...
looks like a missing dependency: `gtksourceview4`
that is right `input-remapper-control --list-devices` does not communicate with the service, and therefore only has the user permissions. The user does not have permissions to read all devices. --- **possible...
maybe this can help: https://bbs.archlinux.org/viewtopic.php?id=273094
Just leaving this here as an idea how to solve this with mapping handlers (from https://github.com/sezanzeb/input-remapper/pull/578#issuecomment-1374673063): > Add a InputConfig.toggle parameter which can solve https://github.com/sezanzeb/input-remapper/issues/547 and https://github.com/sezanzeb/input-remapper/issues/378 by inserting a...
your best bet is to switch to the beta branch. There it is possible to map one axis to another without macros. But this will not solve the issue with...
that would require us to change how combinations work. A possible solution could be the introduction of a `greedy` parameter for the `InputCombination` class. The key-down event would be not...
Or maybe A dialog popup: "do you want to replace `macro` by `recorded stuff` - Confirm/Abort" if there is anything in the text field. This avoids creating invalid macros.
> As default, only record analog input if it's value is over a threshold (maybe 1/3 of max). The threshold is currently at 30% for `EV_ABS` inputs. And at 3...