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: Open top/right corner of desktop #14924

Closed
mkanet opened this issue Feb 27, 2023 · 7 comments
Closed

Quake Mode: Open top/right corner of desktop #14924

mkanet opened this issue Feb 27, 2023 · 7 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@mkanet
Copy link

mkanet commented Feb 27, 2023

Is there a way yet to specify which part of the screen Quake Mode will open? For the last couple of years, I've been using the below utility to add this feature to MS Terminal: https://github.com/flyingpie/windows-terminal-quake which does this perfectly.

Anyway, I'm curious if there's a way to do it natively instead of relying on a 3rd party utility.

PS: I also noticed that native Quake Mode in MS Terminal still draws the acrylic blur effect too slow. Windows-terminal-quake fixes this issue too.

@microsoft-github-policy-service microsoft-github-policy-service bot 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 Feb 27, 2023
@zadjii-msft
Copy link
Member

This might be some combination of

I also noticed that native Quake Mode in MS Terminal still draws the acrylic blur effect too slow. Windows-terminal-quake fixes this issue too.

Could you maybe post a gif/video of what you mean? I'm not sure I can picture what you're describing. This might be one of the things mentioned in #8888, but I wanna be sure

@mkanet
Copy link
Author

mkanet commented Mar 1, 2023

Thanks for your help. Yes, I think those links are what I'm asking.

The problem is that MS Terminal Quake mode doesn't honor the below settings. Also, native MS Terminal Quake mode seems to be super clunky when using Acryllic Blur effect; even on a fast PC.

    "initialCols": 134,
    "initialPosition": "962,0",
    "initialRows": 26,

The expected behavior is exactly as shown in the video below. It opens in the correct part of the screen and animates VERY smoothly with Acryllic Blur effect. I'm currently relying on https://github.com/flyingpie/windows-terminal-quake to handle Quake Mode for MS Terminal since it looks like both issues are still present with MS Terminal.

I uploaded the video clip to youtube so you can see just how smoothly quake mode could be natively.

https://youtu.be/OFrvWorrzBc

@zadjii-msft
Copy link
Member

zadjii-msft commented Mar 1, 2023

Okay yea that sounds like

In general, I'd honestly just recommend globalSummon over quakeMode. You can achieve all the same results, but in a more flexible way.

I'm just gonna bulk call this /dup #8888 since this incorporates a bunch of related feedback. Thanks!

@microsoft-github-policy-service
Copy link
Contributor

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!

@microsoft-github-policy-service microsoft-github-policy-service bot 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 1, 2023
@microsoft-github-policy-service
Copy link
Contributor

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!

2 similar comments
@microsoft-github-policy-service
Copy link
Contributor

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!

@microsoft-github-policy-service
Copy link
Contributor

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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