starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

A solution to the "acrylic-focus" problem, which isn't GPU intensive #9288

New Issue
Closed
opened 2026-01-31 01:50:48 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 01:50:48 +00:00
Owner
Copy Link

Originally created by @AdrienGuimbal on GitHub (Jun 26, 2020).

A solution to the "acrylic-focus" problem, without being GPU intensive

(before everything, sorry if my English is a little bit approximate, I'm French)
A lot of people are complaining about the acrylic background not be working when the terminal isn't in focus.
But instead of displaying a uniform (ugly) background when the window loses focus, it could be possible to "save" the current state of the acrylic background and display it until the window is back in focus.

(I didn't understand the question...)
Ps : Thanks for your work, this new Terminal is extraordinary

Originally created by @AdrienGuimbal on GitHub (Jun 26, 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! --> A solution to the "acrylic-focus" problem, without being GPU intensive <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> (before everything, sorry if my English is a little bit approximate, I'm French) A lot of people are complaining about the acrylic background not be working when the terminal isn't in focus. But instead of displaying a uniform (ugly) background when the window loses focus, it could be possible to "save" the current state of the acrylic background and display it until the window is back in focus. <!-- A clear and concise description of what you want to happen. --> (I didn't understand the question...) Ps : Thanks for your work, this new Terminal is extraordinary
claunia added the Issue-FeatureNeeds-TriageNeeds-Tag-Fix labels 2026-01-31 01:50:48 +00:00
claunia commented 2026-01-31 01:50:49 +00:00
Author
Owner
Copy Link

@JasonWei512 commented on GitHub (Jun 29, 2020):

In fact this should be done by DWM...

@JasonWei512 commented on GitHub (Jun 29, 2020): In fact this should be done by DWM...
claunia commented 2026-01-31 01:50:49 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 4, 2020):

Thanks for the suggestion! You know what, I'm just caving on this issue and suggesting that someone port the brush from Notepads, which supports unfocused acrylic, to the Terminal. We're going to make it an opt-in setting, so users can chose this behavior if they want, but that's going to be the cleanest solution to this problem IMO. This work is going to be tracked over in #7158

@zadjii-msft commented on GitHub (Aug 4, 2020): Thanks for the suggestion! You know what, I'm just caving on this issue and suggesting that someone port the brush from Notepads, which supports unfocused acrylic, to the Terminal. We're going to make it an opt-in setting, so users can chose this behavior if they want, but that's going to be the cleanest solution to this problem IMO. This work is going to be tracked over in #7158
claunia commented 2026-01-31 01:50:49 +00:00
Author
Owner
Copy Link

@harounhajem commented on GitHub (Aug 4, 2020):

@Adriiii I understand the problem but It's not a good solution and it will impact the perceived quality of the terminal, since it may look like a bug. Because the proposal is not following the expected behavior of acrylic glass.

I would advice just using a transparent background or a solid background on a low-end machine.

@harounhajem commented on GitHub (Aug 4, 2020): @Adriiii I understand the problem but It's not a good solution and it will impact the perceived quality of the terminal, since it may look like a bug. Because the proposal is not following the expected behavior of acrylic glass. I would advice just using a transparent background or a solid background on a low-end machine.
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 Issue-Feature Needs-Tag-Fix Needs-Triage
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#9288
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?