jonasBoss

> isn't the recording pipeline also using the default deadzone? No, the recording Pipeline always converts to key-events with a hard-coded threshold.

InputRemapper will not repeat any keys. Except you write a macro which explicitly repeats a key press. All the repeat events are generated by the kernel. I guess you can...

how would you do that for a real device? It might work the same for a virtual one.

Generally that sounds good to me 👍. there are some questions: 1. do we keep the commit history as is? - generally I would say yes. All PRs where squashed...

> have migrations ever caused effort to maintain? It is not really that much effort. Only if we add new migrations we need to update all the related unittests because...

> link is not opening for me (404) it is already on main: https://github.com/sezanzeb/input-remapper#migrating-beta-configs-to-version-2

I refactored a lot of the tests in #263 and #375, so yeah it has been much worse. It might be worth looking into #592 for this. I think having...

Contributions are always welcome 👍. I will happily review any changes you suggest.

can you post the `Supported events` section from `$evtest`? It should look something like this: ``` Input device name: "Sony Interactive Entertainment Wireless Controller Touchpad" Supported events: Event type 0...

That is what I suspected. InputRemapper currently assumes that a ABS_XX axis is always symmetrical. Your device sends ``` Event: time 1670422841.501116, type 3 (EV_ABS), code 40 (ABS_MISC), value 0...