jonasBoss

> If you want this in a 2.0, I would say we stay minimal with the change: > > - remove the pkexec stuff (maybe replaced by development-only [env var](https://github.com/ubunatic/input-remapper/pull/2/files#diff-8d46828515cda696c8e9c4ad14726b07a5a01f518519ab8def95e5b237175236R139)...

since there is no movement on this PR: #123 Here is a fix which can be deployed without touching the dbus-next library ```python def fix_non_returning_decorator(decorator): def fixed_decorator(fn): retval = None...

Better workaround, which does not break async functions: This does rely a bit on dbus-next internals. ```python from dbus_next import service def method(name: str = None, disabled: bool = False):...

Is there anything holding this back that I can do do address? The CI errors don't seem to be related to this PR.

I think an Analog threshold is already possible just not with the UI You can edit the the preset .json file (`~/.config/input-remapper-2/presets//.json`) it should contain the two analog mappings: ```json...

Also I am not sure if this really solves your problem. This will just start each mapping once you have pushed the pedal beyond 50% (beyond the 0 point if...

It is already possible using the aio MessageBus. If you are curious why: https://github.com/altdesktop/python-dbus-next/blob/ab566e16a71bfc9d7e0d29676aa459ec060e72c5/dbus_next/aio/message_bus.py#L345

this seems to be redundant: https://github.com/altdesktop/python-dbus-next/blob/ab566e16a71bfc9d7e0d29676aa459ec060e72c5/dbus_next/aio/message_bus.py#L345

#550 Separates InputEvent from InputConfig

That should work just fine. In fact the macro you provided works for me. I wonder if there might be a race condition somewhere. We did reduce the pause we...