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

Quake Mode multi monitor setup #14038

New Issue
Closed
opened 2026-01-31 03:59:07 +00:00 by claunia · 10 comments
claunia commented 2026-01-31 03:59:07 +00:00
Owner
Copy Link

Originally created by @samirbanjanovic on GitHub (May 29, 2021).

Originally assigned to: @zadjii-msft on GitHub.

I've been toying with quake mode and noticed some odd behaviors when running on multiple monitors, where one is on a vertical orientation. On first summon quake mode dropped down from my desired "main" monitor. Consecutive summons have it split between two monitors but never on a single monitor. I tried changing the monitor and desktop values of the command without luck.

In the attached image you can see that the window dropped down to my left most monitor (which is vertical).
It appears the drop down is tracing location of mouse relative to left|right of center in regards to the entire resolution of the combined screens (?).

If my mouse is towards left of center it will render on left most monitor, with the right edge meeting center of main screen.
image

If my mouse is to the right of center of main screen it renders on the right "half" of the resolution, with the left edge meeting center of main monitor.
image

Last interesting thing to happen is -- if my mouse is on the left edge of my left most screen it renders off screen.
image

Originally created by @samirbanjanovic on GitHub (May 29, 2021). Originally assigned to: @zadjii-msft on GitHub. I've been toying with `quake` mode and noticed some odd behaviors when running on multiple monitors, where one is on a vertical orientation. On first summon quake mode dropped down from my desired "main" monitor. Consecutive summons have it split between two monitors but never on a single monitor. I tried changing the `monitor` and `desktop` values of the command without luck. In the attached image you can see that the window dropped down to my left most monitor (which is vertical). It appears the drop down is tracing location of mouse relative to left|right of center in regards to the entire resolution of the combined screens (?). If my mouse is towards left of center it will render on left most monitor, with the right edge meeting center of main screen. ![image](https://user-images.githubusercontent.com/2653176/120077325-efb21a00-c077-11eb-8a1e-5e3f0a006f71.png) If my mouse is to the right of center of main screen it renders on the right "half" of the resolution, with the left edge meeting center of main monitor. ![image](https://user-images.githubusercontent.com/2653176/120077333-f9d41880-c077-11eb-99f3-d6b6d3cffab4.png) Last interesting thing to happen is -- if my mouse is on the left edge of my left most screen it renders off screen. ![image](https://user-images.githubusercontent.com/2653176/120077359-14a68d00-c078-11eb-9d0f-82952bae4290.png)
claunia commented 2026-01-31 03:59:08 +00:00
Author
Owner
Copy Link

@TomaszGrzmilas commented on GitHub (Jun 1, 2021):

In my case, I got two monitors. On first I have no Windows taskbar, on second I got Windows taskbar located at right monitor edge.

When I run Quake mode on monitor 2 it is looking ok:

image

But when I do Quake mode on monitor 1, Windows Terminal is having gap in place where the Windows taskbar is on second monitor:

image

@TomaszGrzmilas commented on GitHub (Jun 1, 2021): In my case, I got two monitors. On first I have no Windows taskbar, on second I got Windows taskbar located at right monitor edge. When I run Quake mode on monitor 2 it is looking ok: ![image](https://user-images.githubusercontent.com/32311696/120359506-079fcd00-c308-11eb-83df-2331971a0524.png) But when I do Quake mode on monitor 1, Windows Terminal is having gap in place where the Windows taskbar is on second monitor: ![image](https://user-images.githubusercontent.com/32311696/120359612-29994f80-c308-11eb-91ed-7cf6de8e035a.png)
claunia commented 2026-01-31 03:59:08 +00:00
Author
Owner
Copy Link

@brentos99 commented on GitHub (Jun 3, 2021):

I've been having some issues with the quake mode on multi monitors. (love this new feature btw)..

My setup is a 4k landscape monitor above the laptop and a hd portrait monitor next to the that. All 3 monitors have different resolutions and scaling factors.

When opening on the laptop screen it works perfectly, full width of the screen.
When opening on the 4k screen, it only goes to 3/4 width of the screen.
When Opening on the 1080, portrait screen, its width spills over to the 4k screen.

Sometimes it gets confused and doesn't know which is the active screen and opens in the previous window, other times it opens in random places on the screen (usually the middle)

There is also what feels like screen tear in the slide down effect.

Hope this helps in getting the bugs ironed out. If needed, I can provide screenshots.

Brent

@brentos99 commented on GitHub (Jun 3, 2021): I've been having some issues with the quake mode on multi monitors. (love this new feature btw).. My setup is a 4k landscape monitor above the laptop and a hd portrait monitor next to the that. All 3 monitors have different resolutions and scaling factors. When opening on the laptop screen it works perfectly, full width of the screen. When opening on the 4k screen, it only goes to 3/4 width of the screen. When Opening on the 1080, portrait screen, its width spills over to the 4k screen. Sometimes it gets confused and doesn't know which is the active screen and opens in the previous window, other times it opens in random places on the screen (usually the middle) There is also what feels like screen tear in the slide down effect. Hope this helps in getting the bugs ironed out. If needed, I can provide screenshots. Brent
claunia commented 2026-01-31 03:59:09 +00:00
Author
Owner
Copy Link

@nico-abram commented on GitHub (Jun 28, 2021):

I have two monitors, both have the task bar at the bottom, and both are using the regular orientation. However the quake mode terminal has the wrong width. It worked fine yesterday, I'm not sure what's wrong now:
imagen

EDIT: It is now fine after closing it with alt+f4 and opening it again

@nico-abram commented on GitHub (Jun 28, 2021): I have two monitors, both have the task bar at the bottom, and both are using the regular orientation. However the quake mode terminal has the wrong width. It worked fine yesterday, I'm not sure what's wrong now: ![imagen](https://user-images.githubusercontent.com/24706838/123694507-caa7f700-d82f-11eb-92b2-7a3751836c5b.png) EDIT: It is now fine after closing it with alt+f4 and opening it again
claunia commented 2026-01-31 03:59:09 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 7, 2021):

Welp, that's weird. I've been using QM for a while with multi-mon, but never ran into anything like this. Maybe the vertical/horizontal orientation is important here. I'll stick this on 2.0 for now, but if anyone who's actually hitting this could help debug, that'd definitely be appreciated.

@zadjii-msft commented on GitHub (Jul 7, 2021): Welp, that's weird. I've been using QM for a while with multi-mon, but never ran into anything like this. Maybe the vertical/horizontal orientation is important here. I'll stick this on 2.0 for now, but if anyone who's actually hitting this could help debug, that'd definitely be appreciated.
claunia commented 2026-01-31 03:59:09 +00:00
Author
Owner
Copy Link

@nico-abram commented on GitHub (Jul 7, 2021):

Ok I think I can reproduce my issue now. Like I said before, I have two monitors, both have the task bar at the bottom, and both are using the regular orientation.

  1. Open QM terminal with hotkey
  2. Hit winkey+shift+[left or right arrow key] to move it to the other monitor
  3. The terminal now has the wrong size in the second monitor
    imagen
  4. It is already wrong now, but if you move it back to the first screen (With either the QM terminal hotkey or winket+shift+[left or right arrow key] ), it is also wrong on the first monitor (It ends up like my screenshot in the comment above)
@nico-abram commented on GitHub (Jul 7, 2021): Ok I think I can reproduce my issue now. Like I said before, I have two monitors, both have the task bar at the bottom, and both are using the regular orientation. 1) Open QM terminal with hotkey 2) Hit winkey+shift+[left or right arrow key] to move it to the other monitor 3) The terminal now has the wrong size in the second monitor ![imagen](https://user-images.githubusercontent.com/24706838/124823375-7d223d00-df47-11eb-860d-0b0188546f9c.png) 4) It is already wrong now, but if you move it back to the first screen (With either the QM terminal hotkey or winket+shift+[left or right arrow key] ), it is also wrong on the first monitor (It ends up like my screenshot in the comment above)
claunia commented 2026-01-31 03:59:09 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 15, 2021):

notes before I leave for the weekend:

  • WM_WINDOWPOSCHANGING is probably not the right place to do this.
    • It gets called way too often, we don't need to try and enterQuakeMode that many times
    • For whatever reason, doing enterQuakeMode there does calculate the right size, but then the window still ends up at the wrong dimensions. Maybe this is getting followed up with a WM_SIZING or something.
  • Where is the right place to determine that we've moved? WM_MOVING? I suppose that might work
@zadjii-msft commented on GitHub (Jul 15, 2021): notes before I leave for the weekend: * WM_WINDOWPOSCHANGING is probably not the right place to do this. * It gets called way too often, we don't need to try and enterQuakeMode that many times * For whatever reason, doing enterQuakeMode there does calculate the right size, but then the window still ends up at the wrong dimensions. Maybe this is getting followed up with a WM_SIZING or something. * Where is the right place to determine that we've moved? WM_MOVING? I suppose that might work
claunia commented 2026-01-31 03:59:10 +00:00
Author
Owner
Copy Link

@b-hayes commented on GitHub (Jul 26, 2021):

IM having a similar issue. I have horizontal screens layout but they're different resolutions and scaling. My secondary screen is 4k@150% scaling and my primary screen is 1440p. When the terminal opens on the secondary screen it doesn't go all the way across.

image

PS - Also really appreciate this quake console mode. I was doing it manually with AHK and then it wasn't working properly one day and realized you guys baked the feature in using the same hotkey 😅

@b-hayes commented on GitHub (Jul 26, 2021): IM having a similar issue. I have horizontal screens layout but they're different resolutions and scaling. My secondary screen is 4k@150% scaling and my primary screen is 1440p. When the terminal opens on the secondary screen it doesn't go all the way across. ![image](https://user-images.githubusercontent.com/30540495/126919841-bcca1979-9f42-48d8-aad9-790992d78df4.png) PS - Also really appreciate this quake console mode. I was doing it manually with AHK and then it wasn't working properly one day and realized you guys baked the feature in using the same hotkey 😅
claunia commented 2026-01-31 03:59:10 +00:00
Author
Owner
Copy Link

@b-hayes commented on GitHub (Aug 8, 2021):

Actually, is there any way to just turn this off? I want my own implementation back and WT won't let me use this keyboard shortcut for my AHK script anymore.

I thought it was cool but Quake mode is a hindrance I want it gone.

@b-hayes commented on GitHub (Aug 8, 2021): Actually, is there any way to just turn this off? I want my own implementation back and WT won't let me use this keyboard shortcut for my AHK script anymore. I thought it was cool but Quake mode is a hindrance I want it gone.
claunia commented 2026-01-31 03:59:10 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 31, 2021):

:tada:This issue was addressed in #10744, which has now been successfully released as Windows Terminal Preview v1.10.2383.0.🎉

Handy links:

@ghost commented on GitHub (Aug 31, 2021): :tada:This issue was addressed in #10744, which has now been successfully released as `Windows Terminal Preview v1.10.2383.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.10.2383.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
claunia commented 2026-01-31 03:59:10 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 31, 2021):

:tada:This issue was addressed in #10744, which has now been successfully released as Windows Terminal Preview v1.11.2421.0.🎉

Handy links:

@ghost commented on GitHub (Aug 31, 2021): :tada:This issue was addressed in #10744, which has now been successfully released as `Windows Terminal Preview v1.11.2421.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.11.2421.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
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-UserInterface Help Wanted Issue-Bug Priority-2 Product-Terminal Resolution-Fix-Committed
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#14038
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?