Offer "connect/disconnect input device" as a trigger

[GfEW]

Have you checked if an issue already exists for this feature request?

• Nobody else has requested this feature before

What feature would you like added?

The Problem

KeyMapper, as of v4.0.5--foss 247, doesn't seem to offer a way to trigger specific actions upon connect/disconnect of a given input device. Although doing so might stretch the limits of a pure "key mapper", it's so closely related it would make a lot of sense.

Example scenarios include switching the input language after disconnect, or turning NumLock on upon connect (which is notoriously reset on some Android devices).

Suggested Solution

Offer one trigger each for "device connected" and "device disconnected", with the same device selector options like plain key triggers (currently Any device/This device/ID, to be improved).
I don't know if technically feasible, but UX wise, you could even capture it the same way, i. e. press "Tap to record trigger", then connect or disconnect your bluetooth keyboard (provided it's paired already).

App version

4.0.5-foss 247

Device model and manufacturer

diverse

Extra info

• My device is rooted

[jambl3r]

I would personally argue that this is beyond the scope, and would be fiddly for bluetooth devices anyway. Nevertheless I will bring this up with the developer just in case

[sds100]

Yeah, I'm on the edge about this. I can see how it is relating to key mapping because a lot of people are configuring external devices with Key Mapper. On the other hand, I don't know a logical place to put this in the app. Maybe there are only a common subset of useful things to do on device connect/disconnect, that it could live in Settings.

[GfEW]

Thank you both for considering this suggestion.

Although I value the beauty of streamlined UIs that offer exactly those features that "officially make sense", and nothing else, there's sometimes a grey zone where a particular, seemingly fringe feature makes a lot of sense to users in ways you haven't foreseen.

I'm not as much worrying some actions might end up not making sense with a connect/disconnect trigger specifically (e. g. keycode/scancode - just ignore/disable the distinction), but would rather greatly appreciate if there was a way to set up actions that do (which to conceive and judge, in my view, should be up to the user).