-
Notifications
You must be signed in to change notification settings - Fork 228
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The relationship between operating system bit version and high DPI #743
Comments
Not providing 32-bit HD builds is just to reduce release artifacts (currently 53), as 32-bit builds are only used for legacy systems (some functionalities are not implemented for 32-bit builds, search CI build contains 32-bit HD for i18n builds. |
There is misleading info in your post, AVX512 ( |
The 64-bit information in my post comes from the following list. File List
Am I not understanding the list correctly? |
It is worth mentioning that here in the code, AVX2 and x64 are also divided into 2 versions. |
It says Minimum System, x64 builds works fine on 64 bit Win7, Win8, Win10, Win11. nowadays who still daily use 32-bit CPU and system? |
Sorry, I didn't mean to piss you off. Thank you for your patient answer. |
release note is updated like following: File List
Latest development builds (artifacts in Release configuration for each compiler and platform) are available at https://github.com/zufuliu/notepad2/actions and https://ci.appveyor.com/project/zufuliu/notepad2. |
During #732, I learned that in order to reduce resource usage, this project has stopped supporting high DPI for some versions.
But why stop the
Win32
version instead of thex64
version?Below is a table about Windows NT system versions.
Judging from the system support perspective, the priority order of each version can be derived.
AVX2
(Future) >ARM64
(Future) >Win32
(2028 Year) >ARM
(2023 Year) >x64
(2017 Year)Can we resume offering the high DPI version of the
Win32
version and stop offering the high DPI version of thex64
version?The text was updated successfully, but these errors were encountered: