Closed Auties00 closed 2 months ago
@alexmercerind Can you test this PR on your machine? I don’t have access to a Windows 11 machine.
Any chance this could be merged?
Alright, it seems that @alexmercerind isn’t really active these days (at least on this project), so maybe I’ll just merge and publish it anyway. @Auties00, have you checked that your fix doesn’t introduce any regressions on Windows 10?
Alright, it seems that @alexmercerind isn’t really active these days (at least on this project), so maybe I’ll just merge and publish it anyway. @Auties00, have you checked that your fix doesn’t introduce any regressions on Windows 10?
I've checked that and it doesn't cause any issues, yet I've noticed yesterday that if you have a WinSDK that defines the enumeration i added it will go in conflict. I'll push a fix for that
Alright, it seems that @alexmercerind isn’t really active these days (at least on this project), so maybe I’ll just merge and publish it anyway. @Auties00, have you checked that your fix doesn’t introduce any regressions on Windows 10?
I've checked that and it doesn't cause any issues, yet I've noticed yesterday that if you have a WinSDK that defines the enumeration i added it will go in conflict. I'll push a fix for that
ive tested and it works for me, not that a random on the internet can be any justification for merging it. but its a +1 from me
After setting the acrylic effect on Windows 11 with the following code:
Currently, the Window looks like this when focused:
With my fix, it looks like this:
This behaviour is coherent with the native behaviour, for example in the Settings app:
I also created an enum for the DWMWINDOWATTRIBUTE values that the library needs.