Skip to content

Conversation

HeikoKlare
Copy link
Contributor

With the implementation of monitor-specific UI scaling on Windows, an SWT application does not have a static zoom anymore. The zoom will be specific for each shell and the monitor it is currently placed on. As a consequence, when programmatically creating an image, the target zoom at which it will be used is not known when creating the image anymore. Instead, it will depend on the context in which the image is used later on. There are multiple options how to achieve that such an image will still be rendered at the according zoom in a sharp way instead of rendering it at an arbitrary zoom and then scaling it in a blurry way. This snippet demonstrates these different options and also a common way for programmatic image creation that will lead to blurry results.

With the implementation of monitor-specific UI scaling on Windows, an
SWT application does not have a static zoom anymore. The zoom will be
specific for each shell and the monitor it is currently placed on. As a
consequence, when programmatically creating an image, the target zoom at
which it will be used is not known when creating the image anymore.
Instead, it will depend on the context in which the image is used later
on. There are multiple options how to achieve that such an image will
still be rendered at the according zoom in a sharp way instead of
rendering it at an arbitrary zoom and then scaling it in a blurry way.
This snippet demonstrates these different options and also a common way
for programmatic image creation that will lead to blurry results.
Copy link
Contributor

github-actions bot commented Oct 2, 2025

Test Results

  118 files  ±0    118 suites  ±0   9m 39s ⏱️ -41s
4 583 tests ±0  4 547 ✅ ±0  36 💤 ±0  0 ❌ ±0 
  330 runs  ±0    307 ✅ ±0  23 💤 ±0  0 ❌ ±0 

Results for commit e57f0db. ± Comparison against base commit d262fb2.

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.

Snippet for handle recreation support in GC via operation pattern
1 participant