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

Feature request: Ability to change window appearance when window is not in focus #9711

Closed
deadlydog opened this issue Apr 6, 2021 · 2 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@deadlydog
Copy link

We already have the ability to customize the appearance of the Windows Terminal via profiles. I'm requesting that a "lostFocus" profile be supported, where it would take effect when the Windows Terminal is not in focus. This would allow us to give the Windows Terminal a different appearance when not in focus, allowing you to easily differentiate when the window has focus and you can type in it, and when another application has focus. e.g. decrease the acrylicOpacity of the window when it's not in focus. If no "lostFocus" profile is defined, then it would continue to work as it does today.

Since not all of the settings in a profile are related to appearance, another alternative would be to instead support a separate color scheme when the window is not in focus. Really all I'm looking for is a way to easily distinguish when the window has focus or it doesn't. Currently the only visual indicator that the window has focus is the small blinking cursor, and that only shows up if your terminal window isn't scrolled up; if it is scrolled up then there's absolutely no visual indicator that the Windows Terminal has focus, besides the Windows taskbar, which isn't always noticeable, especially with multi-monitor setups.

@deadlydog deadlydog added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Apr 6, 2021
@ghost ghost added Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Apr 6, 2021
@zadjii-msft
Copy link
Member

Boy, are you gonna be excited about this PR we've got in flight: #8392. That's not exactly what you've asked for, but it should accomplish the same goal.

/dup #3062
/dup #2316

@ghost
Copy link

ghost commented Apr 6, 2021

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 closed this as completed Apr 6, 2021
@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 Apr 6, 2021
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. 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