Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

quake mode window doesn't resize when screen width changes in mstsc remote desktop #12785

Closed
Fan-iX opened this issue Mar 29, 2022 · 2 comments
Closed
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@Fan-iX
Copy link

Fan-iX commented Mar 29, 2022

Windows Terminal version

1.12.10393.0

Windows build number

10.0.22581.0

Other Software

mstsc.exe remote desktop

Steps to reproduce

  1. One local PC with two monitors, and one remote PC
  2. Connect to the remote PC using mstsc.exe (full screen)
  3. start wt in quake mode in the remote desktop
  4. move the mstsc.exe window to another monitor and maximize (full screen) it

Expected Behavior

Quake mode window width adjusted to the new screen width

Actual Behavior

Quake mode window width doesn't change, even after hiding and re-showing the window

quake_window

monitor information:
mstsc.exe window moved form [3000×2000, 200% scale]
to [1920×1200, 100% scale] (the screenshot)

@Fan-iX Fan-iX added the Issue-Bug It either shouldn't be doing this or needs an investigation. label Mar 29, 2022
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Mar 29, 2022
@zadjii-msft
Copy link
Member

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #11125 for more discussion.

/dup #11125

@ghost
Copy link

ghost commented Mar 30, 2022

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Mar 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants