-
-
Notifications
You must be signed in to change notification settings - Fork 105
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
Gesture bindings #372
Comments
How about this:
You can only set either an argument, or the properties. All three have only those variants that make sense for that property (i.e. no vertical-only gestures in the horizontal property). I'm still not sure about encoding the finger count into the "key" name.
Examples: currently existing interactive window resize; future interactive window move. For the resize it even makes sense to be able to bind just the horizontal part (since we're a scrolling WM). |
I was looking for a way to set The encoding of the finger count into the key name makes sense to me. |
how about some thing like this:
So that the touchpad gestures are identical to the keyboard shortcuts for focusing columns. this fixes #466 |
I envision the gesture bindings section only for continuous binds, and the regular bind section for discrete binds. |
Do you have any thoughts on forwarding continuous gestures to layer-shell based desktop components? (think being able to pinch in the app menu from anywhere like on macOS) I have previously prototyped that for Wayfire in wf-globalgestures which exposes a custom protocol, but I think I'd be fine with a config-based solution to avoid having Yet Another Protocol, like so (this example would result in that gesture always being forwarded to a client with matching 'namespace' on the current output):
|
Hm, interesting idea. Need to look into it when implementing. |
Add some way to customize gesture bindings. I don't have a concrete design yet, but:
I'm thinking something like a
binds
section, but for gestures. To satisfy 1. and 2., maybe encode number of fingers explicitly into the "key"?This way, I can add new defaults when this section is missing from the config, and when it is present in the config the user will just need to add new gestures manually.
I don't entirely like this though, looks kinda awkward.
Also, I can see a problem in the future where there may be a 2D gesture, and so you will need to be able to bind either
touchpad-swipe-N
to a 2D gesture, or separatetouchpad-swipe-N-horizontal/vertical
to 1D gestures. But also maybe that's not a problem and can just be verified during parsing.Also, this "gestures" section that I have in mind seems to be mainly about continuous gestures (swipe and pinch) and not about discrete gestures like double-resize-click (these seem more fit for the regular binds section).
Also, should it be allowed to bind "vertical" to "horizontal" gestures and vice versa? Maybe not.
The text was updated successfully, but these errors were encountered: