option to make individual keys used in a chord mapping usable.

[yshui]

right now if two buttons are used in a chord mapping, they both become unusable. (e.g. if A + B is mapped to Start, individual presses of either A or B are no longer registered). this effectively means we lose one button.

if i want to create a button i need but does not physically exist on the gamepad, chord mapping get very close to that goal but just come a bit short.

[yshui]

would be nice if there is a fallthrough here if translate_chord returned None:

InputPlumber/src/input/event/evdev/translator.rs

Lines 200 to 203 in 8d9c2ac

	return self
	.translate_chord(event)
	.map(|e| vec![e])
	.unwrap_or_default();

[pastaq]

This is fairly difficult. You need some kind of timing heuristic that can differentiate between chords produced with manual events and firmware produced events which can be highly sensitive and device dependant. You can't unsend a key once you determine it's part of a chord

[yshui]

maybe make it user configurable? keep the current chord mapping as is, add a new option to enable sending events for individual keys that are part of a chord.

more specifically:

current behavior: press A -> nothing, then press B -> send Start.
new behavior when option is enabled: press A -> send A, then press B -> send Start.

i think we can also add a mode shift key. say i set button A as the mode shift. pressing A will not send any events by itself, but will change the events other buttons send.