Users arriving from Logitech Options+ or LogiOps look for a list of behaviours
and instead have to discover that a button does nothing until its diversion is
changed, and that some things are settings with no rule at all. That split is
the usual reason a first rule appears not to fire.
Add a page that walks through one device end to end: which of its buttons can be
diverted and under what names, the settings that need no rules, a diverted button
driving a key combination, mouse gestures, and the thumb wheel — including the
integer argument to the thumb wheel tests, without which a wheel action fires far
too often to be useful.
Also covers what does not carry over from LogiOps: control ids are not used,
key names are X11 key symbols rather than evdev names, and running both daemons
against one device makes settings appear to revert at random.
Records which conditions are limited under Wayland, since actions go through
uinput and do work there, while Modifiers and Process do not.
Contents checked against an MX Master 3S on a Logi Bolt receiver.
danielbanariba