-
Notifications
You must be signed in to change notification settings - Fork 426
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Help wanted, needs to find a way to identify a mouse gesture and a key press. #2726
Comments
Solaar only processes one notification at a time, the first two rules require two - a mouse gesture and a key release. So they will never fire. |
hmmm, first thing, the first two, they actually works perfect on my machine if the last one not added, if that's not the defined behavior. One other thing to notice is that the following rule is not working so maybe that's your designed behavior:
So how can I achieve my purpose then? what I want is to assign back button for one group of mouse gesture and middle button for another. |
You could use KeyIsDown conditions, provided that the key is diverted. |
I tried recently, however, if a key is diverted, it no longer respond to mouse gesture or there's a work around here? |
What do you mean "no longer respond to mouse gesture''? |
I mean when I set e.g back button to diverted, this rule won't work for clearer understanding.
it won't work when I set back button to 'mouse gesture' as well |
Information
solaar --version
andgit describe --tags
):solaar 1.1.11+dfsg-2uname -srmo
):Linux 6.8.0-51-generic x86_64 GNU/Linuxsolaar show
for the target device (if applicable):Is your feature request related to a problem? Please describe.
I'm new to the solaar and just got my hand dirty to replicate my windows config to my new linux machine. I'm now frustrate on the mouse gesture setting. What I want is one like what logi does on windows(and mac of course) that one key can represents five action which are: mouse left, mouse right, mouse up mouse down and key press. I wrote the yaml as follow since the manual says that 'If the last thing that a rule does is execute an action, no more rules are processed for the notification.'
however, this approach is quiet unstable, in most cases, it would does the 'jump to next/prev tab' and 'create new tab' for chrome at the same time, and what I want is that after process the mouse gesture, solarr should not process the following rules, meaning it should not 'create new tab' when the keypress action is done.
A
solaar -ddd
output sample for the gesture shared in fileDescribe the solution you'd like
One notification should only excute the first hit rule, and no more following rules after.
Describe alternatives you've considered
Maybe add an action that can end the rule process or a tag for test?
Additional context
Seems enough.
The text was updated successfully, but these errors were encountered: