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

CTRL+Shift+Scroll should enable acrylic if it's not on already #939

New Issue
Closed
opened 2026-01-30 22:11:59 +00:00 by claunia · 11 comments
claunia commented 2026-01-30 22:11:59 +00:00
Owner
Copy Link

Originally created by @Tuumke on GitHub (May 10, 2019).

When useAcrylic is turned off, ctrl+shift+scroll doesn't enable it. This stops people from adjusting their transparencies.

original text

  • Your Windows build number: (Type ver at a Windows Command Prompt)
    Microsoft Windows [Version 10.0.18362.86]
  • What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots)
    CTRL+Shift+Scroll in cmd.exe works fine with transparency/blurring
    CTRL+Shift+Scrol in Powershell.exe doesnt do a thing
  • What's wrong / what should be happening instead:
    I was under the impression that it would work the same als the cmd.exe.
Originally created by @Tuumke on GitHub (May 10, 2019). When `useAcrylic` is turned off, ctrl+shift+scroll doesn't enable it. This stops people from adjusting their transparencies. ### original text > * Your Windows build number: (Type `ver` at a Windows Command Prompt) Microsoft Windows [Version 10.0.18362.86] > * What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots) > CTRL+Shift+Scroll in cmd.exe works fine with transparency/blurring > CTRL+Shift+Scrol in Powershell.exe doesnt do a thing > * What's wrong / what should be happening instead: > I was under the impression that it would work the same als the cmd.exe.
claunia commented 2026-01-30 22:12:00 +00:00
Author
Owner
Copy Link

@ghvanderweg commented on GitHub (May 10, 2019):

is "useAcrylic" set to "true" in the profile for PowerShell (in %localappdata%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\RoamingState\profiles.json)?

@ghvanderweg commented on GitHub (May 10, 2019): is "useAcrylic" set to "true" in the profile for PowerShell (in %localappdata%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\RoamingState\profiles.json)?
claunia commented 2026-01-30 22:12:00 +00:00
Author
Owner
Copy Link

@Tuumke commented on GitHub (May 10, 2019):

is "useAcrylic" set to "true" in the profile for PowerShell (in %localappdata%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\RoamingState\profiles.json)?

No it wasn't! Thanks so much. Love it so far! :)

@Tuumke commented on GitHub (May 10, 2019): > is "useAcrylic" set to "true" in the profile for PowerShell (in %localappdata%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\RoamingState\profiles.json)? No it wasn't! Thanks so much. Love it so far! :)
claunia commented 2026-01-30 22:12:00 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 10, 2019):

Hmm. This is a good suggestion - if we're not using an acrylic background, the mouse wheel could change it into one.

This is possibly something that wouldn't be too hard for someone to dip their toes into the codebase with. Take a look at the code in TermControl::_MouseTransparencyHandler. The trick is, for the case where we're not using acrylic in the settings, we'd need to set a new flag internally in the TermControl to indicate we've switched to acrylic mode.

@zadjii-msft commented on GitHub (May 10, 2019): Hmm. This is a good suggestion - if we're not using an acrylic background, the mouse wheel could change it into one. This is possibly something that wouldn't be _too_ hard for someone to dip their toes into the codebase with. Take a look at the code in `TermControl::_MouseTransparencyHandler`. The trick is, for the case where we're not using acrylic in the settings, we'd need to set a new flag internally in the TermControl to indicate we've switched to acrylic mode.
claunia commented 2026-01-30 22:12:01 +00:00
Author
Owner
Copy Link

@dkter commented on GitHub (May 10, 2019):

I might be able to try this.

Per #593 acrylic is disabled on inactive windows, but should it be possible to enable transparency without the acrylic on inactive windows to make the difference less jarring?

@dkter commented on GitHub (May 10, 2019): I might be able to try this. Per #593 acrylic is disabled on inactive windows, but should it be possible to enable transparency without the acrylic on inactive windows to make the difference less jarring?
claunia commented 2026-01-30 22:12:01 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 10, 2019):

See, we don't even know if there's a way to get non-acrylic transparency. If you could research that, that'd be even more appreciated. I'd think for the time being though, acrylic-backed transparency should be fine

@zadjii-msft commented on GitHub (May 10, 2019): See, we don't even know if there's a way to get non-acrylic transparency. If you could research that, that'd be even more appreciated. I'd think for the time being though, acrylic-backed transparency should be fine
claunia commented 2026-01-30 22:12:01 +00:00
Author
Owner
Copy Link

@dkter commented on GitHub (May 10, 2019):

Yeah, at the moment it seems like the only way to get native transparency is through acrylic. Oh well. Consistency, I guess.

@dkter commented on GitHub (May 10, 2019): Yeah, at the moment it seems like the only way to get native transparency is through acrylic. Oh well. Consistency, I guess.
claunia commented 2026-01-30 22:12:02 +00:00
Author
Owner
Copy Link

@PhMajerus commented on GitHub (May 11, 2019):

I knew my Win32 GDI skills could still be useful 😄

The Win32 way to achieve transparency and alpha blending is through layered windows (Win2K and later if I remember correctly):
https://docs.microsoft.com/en-us/windows/desktop/winmsg/window-features#layered-windows

Try this for example:

LONG lExStyle = GetWindowLong(hWnd, GWL_EXSTYLE);
lExStyle |= WS_EX_LAYERED;
SetWindowLong(hWnd, GWL_EXSTYLE, lExStyle);
SetLayeredWindowAttributes(hWnd, RGB(0, 0, 0), 192, LWA_ALPHA);

I wouldn't recommend it for anything else than a very slight transparency though, since without the ability to blur the background, it would make the console harder to read.

@PhMajerus commented on GitHub (May 11, 2019): I knew my Win32 GDI skills could still be useful 😄 The Win32 way to achieve transparency and alpha blending is through layered windows (Win2K and later if I remember correctly): https://docs.microsoft.com/en-us/windows/desktop/winmsg/window-features#layered-windows Try this for example: ``` LONG lExStyle = GetWindowLong(hWnd, GWL_EXSTYLE); lExStyle |= WS_EX_LAYERED; SetWindowLong(hWnd, GWL_EXSTYLE, lExStyle); SetLayeredWindowAttributes(hWnd, RGB(0, 0, 0), 192, LWA_ALPHA); ``` I wouldn't recommend it for anything else than a very slight transparency though, since without the ability to blur the background, it would make the console harder to read.
claunia commented 2026-01-30 22:12:02 +00:00
Author
Owner
Copy Link

@FoxInFlame commented on GitHub (May 12, 2019):

I wouldn't recommend it for anything else than a very slight transparency though, since without the ability to blur the background, it would make the console harder to read.

Although, this is what has been done in previous CMDs until now afaik. I remember the window being quite hard to read when I lowered the opacity thinking it would blur the background and it didn't.

@FoxInFlame commented on GitHub (May 12, 2019): > I wouldn't recommend it for anything else than a very slight transparency though, since without the ability to blur the background, it would make the console harder to read. Although, this is what has been done in previous CMDs until now afaik. I remember the window being quite hard to read when I lowered the opacity thinking it would blur the background and it didn't.
claunia commented 2026-01-30 22:12:02 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jun 11, 2019):

I think this is a duplicate of #603, actually.

@DHowett-MSFT commented on GitHub (Jun 11, 2019): I think this is a duplicate of #603, actually.
claunia commented 2026-01-30 22:12:02 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jun 11, 2019):

Oh, I see. Okay. I'll repurpose this.

@DHowett-MSFT commented on GitHub (Jun 11, 2019): Oh, I see. Okay. I'll repurpose this.
claunia commented 2026-01-30 22:12:02 +00:00
Author
Owner
Copy Link

@Summon528 commented on GitHub (Jun 14, 2019):

I was playing around with this and was trying to switch the background to an acrylic brush on scroll. However, this makes me wonder why do we even need a useAcrylic option or a solid background brush since setting acrylicOpacity: 1 has the exact effect as useAcrylic: false

@Summon528 commented on GitHub (Jun 14, 2019): I was playing around with this and was trying to switch the background to an acrylic brush on scroll. However, this makes me wonder why do we even need a `useAcrylic` option or a solid background brush since setting `acrylicOpacity: 1` has the exact effect as `useAcrylic: false`
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 Issue-Bug Needs-Tag-Fix Priority-3 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#939
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?