starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Touch Zoom with two fingers don't work on Touch screen (but it works on Touch Pad) #4390

New Issue
Open
opened 2026-01-30 23:45:48 +00:00 by claunia · 2 comments
claunia commented 2026-01-30 23:45:48 +00:00
Owner
Copy Link

Originally created by @DrPepperBianco on GitHub (Oct 10, 2019).

Description of the new feature/enhancement

When I use two finger to zoom in or out (actually making text bigger or smaller), it works on my touch pad. But it actually don't work on my touch screen.

I think the experience would be much smoother if it worked the same on the touch pad and the touch screen.

What I also get is, if I scroll with finger on the touch screen it works. If I try to scroll with two fingers it flickers, as if the program doesn't realize I using two fingers and tries to read both inputs.

So the case with multiple fingers should probably be detected and handled specifically.

Proposed technical implementation details (optional)

If I use two fingers on the touch screen and move them together or away from each other the font size should decrease or increase respectively, exactly as it is now if I do that on the touch screen.

Originally created by @DrPepperBianco on GitHub (Oct 10, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement When I use two finger to zoom in or out (actually making text bigger or smaller), it works on my touch pad. But it actually don't work on my touch screen. I think the experience would be much smoother if it worked the same on the touch pad and the touch screen. What I also get is, if I scroll with finger on the touch screen it works. If I try to scroll with two fingers it flickers, as if the program doesn't realize I using two fingers and tries to read both inputs. So the case with multiple fingers should probably be detected and handled specifically. <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> # Proposed technical implementation details (optional) If I use two fingers on the touch screen and move them together or away from each other the font size should decrease or increase respectively, exactly as it is now if I do that on the touch screen. <!-- A clear and concise description of what you want to happen. -->
claunia commented 2026-01-30 23:45:49 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Oct 12, 2019):

This should be a fairly easy thing to implement. Adding the Help-Wanted tag if anybody wants to hop on. The work should be done in the TermControl.cpp file. There's a few pointer-related functions (i.e.: pointerMoved, pointerClick, etc.) that already handle the mouse movements and a few touch events. Now just a matter of expanding on the touch events.

@carlos-zamora commented on GitHub (Oct 12, 2019): This should be a fairly easy thing to implement. Adding the Help-Wanted tag if anybody wants to hop on. The work should be done in the TermControl.cpp file. There's a few pointer-related functions (i.e.: pointerMoved, pointerClick, etc.) that already handle the mouse movements and a few touch events. Now just a matter of expanding on the touch events.
claunia commented 2026-01-30 23:45:49 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (May 12, 2020):

https://docs.microsoft.com/en-us/windows/uwp/design/input/touch-interactions

Just linking this here for when I (or somebody else) comes by 😊

@carlos-zamora commented on GitHub (May 12, 2020): https://docs.microsoft.com/en-us/windows/uwp/design/input/touch-interactions Just linking this here for when I (or somebody else) comes by 😊
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-TerminalControl Help Wanted Issue-Bug Priority-2 Product-Terminal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#4390
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?