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.
* Fix punctuation and language in rules.md
Fixed a few cases of backquote mistakes, unescaped <>, and misc language typos.
Took the liberty to unitalicise the third paragraph. Obviously it's important, but an entire paragraph in italics is hard to read.
I noticed there were two slightly different paragraphs about Setting conditions, which I assume is a mistake. I don't know which is better than the other, so I simply moved them next to each other for ease of comparison and manual merging/editing.
* Fixed erroneous backquote in rules.md
Fixed a ` which should have been a <. Error introduced by myself in the first place!
- Track `key_up` key in addition to `key_down`
- Support `pressed` or `released` action in `Key` condition
- Add radio button to KeyUI to represent `pressed` or `released`
* Add more robust mouse gesture support
- Remove existing mouse-* Test types
- Add new 'Mouse Gesture' Condition
- Implement Rule Editor UI for it
- Add support for diverted buttons
- Added diagonal mouse gesture directions
Allows you to chain multiple movements/buttons (for instance, moving the mouse up and then left) together into a single mappable gesture.
* Update docs
* Cleanup
Fix inconsistent indenting
Fix possible overwriting of built-in
Fix 'Mouse Gesture' Condition rule not starting with an initial Action field
* Make flake8 happy
* yapf
* Document no-op and make it more apparent
* Make changes to Mouse Gesture UI suggested/submitted by viniciusbm.
Co-authored-by: Apeiron <apeiron@none>
Co-authored-by: Peter F. Patel-Schneider <pfpschneider@gmail.com>
danielbanariba
Peter F. Patel-Schneider
MattHag
Swapnil Devesh
John Veness
Kian-Meng Ang
Vinícius
Karthik Nishanth
ApeironTsuka