Skip to content

Use auto-scale "nearest" by default in Windows #2910 #2051

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

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

fedejeanne
Copy link
Contributor

@fedejeanne fedejeanne commented Apr 23, 2025

Defaulting to "smooth" creates blurry images when first displaying the image in a monitor with a high zoom level (e.g. 200%).

This is a temporary workaround until #2052 is properly fixed.

The auto-scale method can still be manually set to "smooth" by setting this VM argument: -Dswt.autoScale.method=smooth

FIXME

This PR is just a workaround and I am only keeping it here in store in case there is no proper fix in time for M2. I'll keep it drafted until noon but feel free to review now.

Screenshots

When starting the workbench in a monitor at 200% zoom level and with monitor-specific UI scaling enabled. (original screenshots.zip)

In green you can see which images look better using the nearest scale method (and in rot, the same images when using smooth scaling, for comparison).

Auto-scale method nearest (the new default when applying this PR)
image

Auto-scale method smooth (the previous default)
image

Defaulting to "smooth" creates blurry images when first displaying the
image in a monitor with a high zoom level (e.g. 200%).

This is a temporary workaround until
https://github.com/eclipse-platform/eclipse.platform.ui/issues/2910 is
properly fixed.
Copy link
Contributor

Test Results

   545 files  + 6     545 suites  +6   31m 32s ⏱️ + 4m 15s
 4 373 tests +37   4 355 ✅ +35   18 💤 +3  0 ❌  - 1 
16 634 runs  +37  16 496 ✅ +35  138 💤 +3  0 ❌  - 1 

Results for commit 8481886. ± Comparison against base commit 2a50eae.

@HeikoKlare
Copy link
Contributor

This would basically render the SDK unusable on HiDPI monitors when using Windows 🙁
So from my side, this is not an acceptable workaround.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants