microsoft / microsoft/WindowsAppSDK
Exploring New Windows Touch Based Gestures
@pranavhippargi is already working on this.
Since Sep 2, 2020.
- Dominant language
- C++
- Stars
- 4.7k
- Forks
- 471
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 28
Description
**Summary**
Microsoft is considering introducing additional touch-based gestures in Windows to make it easier for users to complete a variety of tasks using touch. We would like your feedback regarding how this work would impact your application.
**Rationale**
The introduction of a variety of new touch gestures into Windows would be intended to accelerate common & important tasks for customers. The greatest customer benefit will come if these gestures are consistent & learnable across the operating system. However, this could potentially create application compatibility issues for gestures within your app because gestures which require more than two fingers will be routed to the OS instead of the application.
We would like to know how this proposed OS feature would impact your application if the application already uses more than two fingers for gestures. While we have a generic proposal in mind, we are looking into alternatives.
**Scope**
If implemented, any touch-screen gesture that consists of more than two fingers will be routed to the OS by default and applications that rely on three-or-more finger gestures will not receive that input in the default configuration.
Additionally, this would be the default behavior for Windows devices (shipping as On by Default), though we will allow users to turn off the OS gesture in Settings. If the setting is turned off the if the application uses more than two fingers for a gesture, the contacts will be routed to the application directly.
Our current design proposal is that applications will not have the ability to programmatically turn off the Global User Setting to allow users to be in control of their Settings and their experience on Windows. However, since we want to maintain application compatibility, we are exploring different pathways to maintain application compatibility for apps on Windows which uses more than two fingers to trigger a gesture. One example is to provide applications the ability to query for the setting and prompt the user to navigate to settings and change it.
**Open Questions**
Does your application currently use gestures that consist of three or more touch points?
If yes,
• What kind of application / experience does this provide?
• How would this change in the default behavior impact your application?
• Would a global user setting be adequate or would you want your individual app to be able to Opt-in to an app-specific override that would allow your application to receive this class of gesture input when being used?
• Do you have any other feedback regarding this proposed feature?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.