The native titlebar is not supposed to be visible at all and the header (Search, Playlist, CRT, Settings, ultraSID logo and window controls) are supposed to be 32 pixels higher up.
All mouse coordinates received are offset by the titlebar border thickness (so like 20-30 pixels in the Y-direction, and maybe 4-5 pixels in the X-direction).
When removing the setDropShadowEnabled ( false ); call everything looks as its supposed to.
Yes, the system corners and drop shadow can only be enabled/disabled simultaneously (well, as far as I can tell). If you want the system to round the window corners, then you need to leave the drop shadow enabled. I don’t think there’s really any downside to this; the drop shadow in Windows 11 seems very fast and it looks nice, too.
To avoid ambiguity, the drop shadow for opaque JUCE windows is now provided by the OS on both Windows 10 and 11. This means it should look a bit nicer and perform better than the old JUCE drop shadower. A disadvantage of this approach is that the same app will have different shadows on Windows 10 and 11; an advantage is that on any given system, shadows in JUCE apps should appear consistent with shadows of other apps.
I 100% agree. I just wanted to point it out. I originally turned the shadow off because it was square, which didn’t look great with a rounded window, and it caused the content of the window to flicker when resizing. The flicker was resolved with a prior commit a few weeks ago, and now that the OS draws the shadow, there is no reason to turn it off anymore.