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.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |