-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Make fancyzones touch friendly. #376
Comments
@SeraphimaZ Think there's possibilities in detecting touch and/or pen input? |
We can try it with the |
I got this working with GESTURESIGN from Microsoft Store. |
If no one is working on it, I can give it a shot. On top of single-finger-holding to activate, I'd also like to consider 1-hand-touch scenario, where another hand might be holding e.g. a Surface. I would implement double-tap-to-activate, and double-tap-to-deactivate. So a user could start dragging a window with index finger, and then double tap with middle finger to activate zone. The middle finger doesn't need to keep touching the screen to keep activating the zone - this activation is edge-triggered. To stop zone activation, just double-tap again.
|
Sadly it seems it's not doable. There is no way to hook globally for |
Summary of the new feature/enhancement
People with touch inputs are unable to use the Shift key to activate zones.
While zones can always stay active if toggle is disabled, windows are the not able to be dragged without snapping.
This would be one of the solutions for usage of Fancy zones for people with only touch input available.
Proposed technical implementation details (optional)
My suggestion is to add another toggle that will activate touch control.
Parallel to the shift key, zones are to be activated when window is dragged and another 1 finger is touching the screen (So 2 fingers 1 dragging [1st finger], 1 touching [2nd finger]).
Zones would disappear if [2nd finger] is lifted, and reappear if [2nd finger] is placed on the screen, the first finger would still be dragging the window.
The text was updated successfully, but these errors were encountered: