microsoft / microsoft/microsoft-ui-xaml
GestureRecognizer minimum contact count properties are missing
- Dominant language
- C++
- Stars
- 8.4k
- Forks
- 942
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 105
Description
### Describe the bug
The UWP [GestureRecognizer](https://learn.microsoft.com/en-us/uwp/api/windows.ui.input.gesturerecognizer?view=winrt-26100) has several properties allowing us to specify the minimum number of contact points for a gesture like [GestureRecognizer.TranslationMinContactCount](https://learn.microsoft.com/en-us/uwp/api/windows.ui.input.gesturerecognizer.translationmincontactcount?view=winrt-26100).
The WinAppSDK [GestureRecognizer](https://learn.microsoft.com/en-us/windows/windows-app-sdk/api/winrt/microsoft.ui.input.gesturerecognizer.-ctor?view=windows-app-sdk-1.6) does not longer have those properties.
I need to restrict the gestures to 2 contacts interactions. Those APIs should be re-added on WinAppSDK to have the same feature level as in UWP.
### Steps to reproduce the bug
Create a WinAppSDk application and try to set the [GestureRecognizer.TranslationMinContactCount](https://learn.microsoft.com/en-us/uwp/api/windows.ui.input.gesturerecognizer.translationmincontactcount?view=winrt-26100) property
### Expected behavior
_No response_
### Screenshots
_No response_
### NuGet package version
Windows App SDK 1.7 Experimental 3: 1.7.250127003-experimental3
### Packaging type
Packaged (MSIX)
### Windows version
Windows 11 version 24H2 (22621, October 2024 Update)
### IDE
Visual Studio 2022
### Additional context
_No response_
Contributor guide
Research direction
Start with the WinAppSDK GestureRecognizer API and compare it with the linked UWP GestureRecognizer documentation, especially the minimum contact count properties. Trace the existing WinAppSDK gesture recognizer implementation and its tests, then verify that the corresponding properties support restricting gestures to two contacts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- api, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100