Revert "SetThreadDpiAwareness for host error dialog" #85773
Conversation
This reverts commit 6f36be5.
ghost
assigned
|
Tagging subscribers to this area: @vitek-karas, @agocke, @VSadov Issue DetailsReverts #81930 There is an issue with the Windows TaskDialog where expanding/collapsing the detail area will result in incorrect resizing of the window when the DPI awareness of the process and thread are not the same. Instead of explicitly making the thread starting the dialog DPI aware, we just leave it whatever the process is set to. This means that if the developer specified a manifest that made their application DPI aware, the dialog will be non-blurry, but if the developer did not, it will remain blurry on high DPI. Fixes #85571
|
|
Actual build shows the checks have completed successfully - the check status is just not updated here. |
Reverts #81930
There is an issue with the Windows TaskDialog where expanding/collapsing the detail area will result in incorrect resizing of the window when the DPI awareness of the process and thread are not the same. Instead of explicitly making the thread starting the dialog DPI aware, we just leave it whatever the process is set to. This means that if the developer specified a manifest that made their application DPI aware, the dialog will be non-blurry, but if the developer did not, it will remain blurry on high DPI.
Fixes #85571