And although I'm very happy to know it finally made to the preview release (and hopefully to the public releases soon). Considering the time it's been in development since then I had expected this feature to be available already.
I've been stuck in LTSC land for a long time, and just gave a try at Windows 11 today. The blog post doesn't say anything about the opacity field (new in the 1.12, per your link) and what's more, it was released in the preview build. I wasn't even aware the PR meant that the feature was released. It's just that "we're going to track this to a single issue because too many yadda yadda duplicate yadda yadda". Well, in the post where you closed the issue I didn't see anything about "it's been released". Would you like something more official than that? That thread was closed by a PR, which you'll note was released in 1.12, which you can also find out about in the release notes, or reading the release blog post. Thanks for the If you'd read the thread, you'd find my post where I closed this issue, where I link it to #603 as a duplicate. Oh I didn't know that, I agree that a comment would've been nice. But yes a comment here to say that would have been nice. Its available in the latest preview build now. Is there any progress regarding this feature, officially from MS? I disagree this issue should be closed, such a feature like this has been available in linux terminals ever since compwiz or other compositors were available almost two decades ago. I wanted to set the terminal transparent and I get a horrible blur along with the acrylic that I want to remove, I don't want the blur, I just want the window transparency while keeping the titlebar/borders opaque and no weird AHK hacks or 3rd-party terminals.
So the MS bot closed this issue with no reason because it's a mindless bot, yet the issue is still ongoing as of date. I even use it now for Spotify and some dark browser windows such as Github in dark mode, I am so happy because other than this strange Acrylic mess the new Windows Terminal is awesome, a perfect package and probably the best terminal experience across OSes. I am a bit surprised that you downtalk such a brilliant solution, did you try exactly this solution with AHK and script? If not pls do, this solution is amazing, feels more polished than any macOS or Linux terminal and doesn't have any flaw, not a single one. If "vintage" is internal MS lingo then it's wrong, detached from your user base and should be changed.Īlso multiple panes work like charm, see below. Also that you call it "vintage-style" doesn't make sense to me-this is exactly how users want transparency, no on and off on focus, no mandatory blur, no random opaque backgrounds/tabs/headers, no resource hog, no blurry fonts. In your examples in the other issue your transparency is way too low, so ofc it looks bad, no surprise. It depends very much on the transparency level which solution allows to be set granularly. If you're manually changing the opacity of the entire window, things are gonna be Can't follow. This may take a bit of refactoring of the Cascadia architecture, but I see no reason why it wouldn’t be able to be done. After that we should be able to draw whatever we want on top of the transparent background window. If it does so in a way that would be unsatisfactory, we can then use that same function to set the alpha of the child HWNDs to 255 (opaque), then clear the child windows with a transparent color to erase the default background fill. That being said, wouldn’t we be able to use SetLayeredWindowAttributes on the root HWND, just as conhostV2 does? As I understand the docs, this should also affect the child windows. How ironic given the function’s name, huh? AFAICT, this doesn’t present any security issues, as the app cannot read the contents of the background shown, as it is processed entirely within dwm.exe. The really old, Vista-era API DwmEnableBlurBehindWindow, if called on Windows 10, changes the window background to a semi-transparent black, without a blur. I have found (at least one) way to accomplish this effect, but not via UWP.