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

Problems when used with Mouse Without Borders #7927

New Issue
Open
opened 2026-01-31 01:16:00 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 01:16:00 +00:00
Owner
Copy Link

Originally created by @strandloper on GitHub (May 4, 2020).

Environment

Windows build number: 10.0.18363 (on LOCAL computer) & 10.0.18362 (on CONNECTED computer)
Windows Terminal version (if applicable): 0.11.1191.0 (on BOTH computers)

Any other software?
Mouse Without Borders version 2.1.8.0105 from http://www.aka.ms/mm

Steps to reproduce

When using Mouse Without Borders to share mouse and keyboard between two computers, run Windows Terminal on both the LOCAL and CONNECTED computer.

Expected behavior

Windows Terminal is expected to work correctly on both computers.

Actual behavior

Windows Terminal works perfectly on the LOCAL computer, i.e. the one that has the mouse and keyboard connected to it. But on the CONNECTED computer Windows Terminal is only semi-usable. On opening a tab with the default console is opened and is fully usable for keyboard interaction. But the entire Windows Terminal window does not accept mouse interaction. This includes the open console (text cannot be selected with mouse), Terminal controls (new tab and menu pulldown cannot be clicked) and window controls (minimise, maximise and close buttons cannot be clicked, to close must use Close window on taskbar icon's context menu). Drag handles do appear over window edges and corners and the window can be resized. Additionally the mouse pointer is not always correctly drawn over the window, often being drawn as the up/down sizing handle when over the console; if the pointer is then moved to the title bar or out of the window and back, the correct arrow pointer is drawn.

I am using a wireless Logitech MX Ergo trackball on the LOCAL computer and a wireless Logitech M570 trackball on the CONNECTED computer. The MX Ergo is dual channel and bound to the receivers on both computers and the terminal behaviour is the same regardless of whether the LOCAL computer channel is connected and the mouse is being shared via Mouse Without Borders, or whether the CONNECTED computer channel is connected and the mouse is thus native to the CONNECTED computer. Additionally the window misbehaviour persists when the single channel M570 connected only to the CONNECTED computer is used.

Closing Terminal, stopping Mouse Without Borders and disabling it's service then re-running Terminal makes no difference, the problem persists. However, after restarting Windows with the Mouse Without Borders service disabled, Terminal behaves correctly and accepts mouse interaction. Finally after enabling the Mouse Without Borders service again (set to Automatic) and restarting Terminal works correctly even with the mouse from the LOCAL computer. Thus it would seem to have been some transient problem and given that and the fairly edge case nature of the usage, you may choose not to investigate further but I thought I should report this in any case.

Originally created by @strandloper on GitHub (May 4, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: 10.0.18363 (on LOCAL computer) & 10.0.18362 (on CONNECTED computer) Windows Terminal version (if applicable): 0.11.1191.0 (on BOTH computers) Any other software? Mouse Without Borders version 2.1.8.0105 from http://www.aka.ms/mm ``` # Steps to reproduce When using Mouse Without Borders to share mouse and keyboard between two computers, run Windows Terminal on both the LOCAL and CONNECTED computer. # Expected behavior Windows Terminal is expected to work correctly on both computers. # Actual behavior Windows Terminal works perfectly on the LOCAL computer, i.e. the one that has the mouse and keyboard connected to it. But on the CONNECTED computer Windows Terminal is only semi-usable. On opening a tab with the default console is opened and is fully usable for keyboard interaction. But the entire Windows Terminal window does not accept mouse interaction. This includes the open console (text cannot be selected with mouse), Terminal controls (new tab and menu pulldown cannot be clicked) and window controls (minimise, maximise and close buttons cannot be clicked, to close must use Close window on taskbar icon's context menu). Drag handles do appear over window edges and corners and the window can be resized. Additionally the mouse pointer is not always correctly drawn over the window, often being drawn as the up/down sizing handle when over the console; if the pointer is then moved to the title bar or out of the window and back, the correct arrow pointer is drawn. I am using a wireless Logitech MX Ergo trackball on the LOCAL computer and a wireless Logitech M570 trackball on the CONNECTED computer. The MX Ergo is dual channel and bound to the receivers on both computers and the terminal behaviour is the same regardless of whether the LOCAL computer channel is connected and the mouse is being shared via Mouse Without Borders, or whether the CONNECTED computer channel is connected and the mouse is thus native to the CONNECTED computer. Additionally the window misbehaviour persists when the single channel M570 connected only to the CONNECTED computer is used. Closing Terminal, stopping Mouse Without Borders and disabling it's service then re-running Terminal makes no difference, the problem persists. However, after restarting Windows with the Mouse Without Borders service disabled, Terminal behaves correctly and accepts mouse interaction. Finally after enabling the Mouse Without Borders service again (set to Automatic) and restarting Terminal works correctly even with the mouse from the LOCAL computer. Thus it would seem to have been some transient problem and given that and the fairly edge case nature of the usage, you may choose not to investigate further but I thought I should report this in any case.
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-Input Issue-Bug Needs-Author-Feedback Needs-Repro Needs-Triage 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#7927
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?