p0nce
p0nce
Multithreaded mutex creation is thread-safe now, but not their destruction.
 Testing the following hosts: - [x] FLStudio => Per Monitor v1 - [x] Live => unaware - [x] REAPER => Per Monitor v1 - [x] Orion => unaware -...
Interesting: the window get to know the DPI, but when DPI-aware is free to choose its own size. So there isn't necessarily a need for resizer, when multiple sizes are...
If resizer is used, it mustn't be on the windowing side, but in the GUIGraphics side. Only the window need to know a "DPI" apparently, but it resize the client...
Apparently we can have Hi-DPI in hosts that don't support it somehow? https://docs.microsoft.com/en-us/windows/win32/hidpi/high-dpi-improvements-for-desktop-applications
Bitwig wrapper (Bitwig is itself Hi-DPI awareness context v2) doesn't have plugin with DPI awareness, as it seems.
Waveform get the right DPI in `WM_DPICHANGED`, however the window is not resized to be larger.
Test `DPI_HOSTING_BEHAVIOR` and `DPI_AWARENESS_CONTEXT` before window creation, and whether the window is stretched in the end : - [x] FLStudio => `DPI_HOSTING_BEHAVIOR_DEFAULT` and `DPI_AWARENESS_PER_MONITOR_AWARE`, Context change OK but not all...
IPlug compares the Windows DPI to the monitor DPI to detect DPI change, which could be alright?
One real problem in Hi-DPI is the shit tier upsampling done by Windows when `DPI_AWARENESS_UNAWARE`. There is a better GDI upsampling available in Windows 10, hopefully it becomes the default...