feat(windows): map multitouch input to primary display

[JamesLewisLiu]

Description

Add an optional setting in Windows branch that maps native multitouch input from streaming clients to the current primary display instead of the streamed display, useful in some cases like this

The mapping preserves normalized touch positions, accounts for differing display resolutions, scaling, virtual desktop offsets, and letterboxed client content, and refreshes the display topology for each event. If the primary display cannot be determined, touch input falls back to the streamed display.

The option is disabled by default and is shown only on Windows when mouse input and native pen/touch support are enabled. Pen, absolute mouse, and regular mouse input remain unchanged.

Add configuration documentation and unit tests covering display selection, coordinate mapping, invalid display layouts, pointer compatibility flags, and default configuration behavior.

Tested on Windows AMD64 using modified Moonlight clients on iOS and Android (Since the original one doesn't support multitouch).

Screenshot

Issues Fixed or Closed

Roadmap Issues

Type of Change

• feat: New feature (non-breaking change which adds functionality)
• fix: Bug fix (non-breaking change which fixes an issue)
• docs: Documentation only changes
• style: Changes that do not affect the meaning of the code (white-space, formatting, missing semicolons, etc.)
• refactor: Code change that neither fixes a bug nor adds a feature
• perf: Code change that improves performance
• test: Adding missing tests or correcting existing tests
• build: Changes that affect the build system or external dependencies
• ci: Changes to CI configuration files and scripts
• chore: Other changes that don't modify src or test files
• revert: Reverts a previous commit
• BREAKING CHANGE: Introduces a breaking change (can be combined with any type above)

Checklist

• Code follows the style guidelines of this project
• Code has been self-reviewed
• Code has been commented, particularly in hard-to-understand areas
• Code docstring/documentation-blocks for new or existing methods/components have been added or updated
• Unit tests have been added or updated for any new or modified functionality

AI Usage

See our AI usage policy.

• None: No AI tools were used in creating this PR
• Light: AI provided minor assistance (formatting, simple suggestions)
• Moderate: AI helped with code generation or debugging specific parts
• Heavy: AI generated most or all of the code changes

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud