This reverts commit 1364b199b4
.
3 ways we can choose:
1. PerMonitorV2: it would be the ideal solution if there were no custom control in Notepad++ : some part of the custom controls like panels and Find dialog are not rendered properly in PerMonitorV2 mode.
2. PerMonitor: in v7.9.3 WM_DPICHANGED message was not processed and that makes Notepad++ unusable under a high resolution monitor.
3. Without "PerMonitor" feature: (as in v7.9.2), it will be a little bit blurry, but at least the system resizes all parts of application correctly
This commit revert the modification in v7.9.3 and go back to the way in v7.9.2 (Without "PerMonitor" feature).
It's not easy to solve this issue, all I can do is choose the "less worst" way, just like people in world-wide vote for choosing their political leader.
Fix #9513, fix #9579
pull/9607/head
parent
4b0010c4c3
commit
47ca5281fe
@ -1,9 +1,9 @@
|
||||
<?xml version='1.0' encoding='UTF-8' standalone='yes'?>
|
||||
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
|
||||
<asmv3:application xmlns:asmv3="urn:schemas-microsoft-com:asm.v3">
|
||||
<asmv3:windowsSettings>
|
||||
<dpiAware xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">true</dpiAware>
|
||||
<dpiAwareness xmlns="http://schemas.microsoft.com/SMI/2016/WindowsSettings">PerMonitor</dpiAwareness>
|
||||
<asmv3:windowsSettings
|
||||
xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">
|
||||
<dpiAware>true</dpiAware>
|
||||
</asmv3:windowsSettings>
|
||||
</asmv3:application>
|
||||
</assembly>
|
||||
</assembly>
|
Loading…
Reference in new issue