Skip to content

Conversation

@ShahzaibIbrahim
Copy link
Contributor

Having the scale factor being based on the screen DPI leads to unexpected result e.g. Image too big/small. Having a screen dpi independent factor leads to consistent results.

@ShahzaibIbrahim ShahzaibIbrahim linked an issue Dec 10, 2025 that may be closed by this pull request
1 task
@github-actions
Copy link
Contributor

github-actions bot commented Dec 10, 2025

Test Results

  176 files  ±0    176 suites  ±0   25m 20s ⏱️ +18s
4 672 tests ±0  4 650 ✅ ±0  22 💤 ±0  0 ❌ ±0 
  482 runs  ±0    476 ✅ ±0   6 💤 ±0  0 ❌ ±0 

Results for commit a4430dd. ± Comparison against base commit 1bc596e.

♻️ This comment has been updated with latest results.

Having the scale factor being based on the screen DPI leads to
unexpected result e.g. Image too big/small. Having a screen dpi
independent factor leads to consistent results.
Copy link
Contributor

@HeikoKlare HeikoKlare left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For the remaining usages of Device#getDPI(), this PR needs to adds according warnings suppressions.
On Windows, I currently see these three remaining usages of the method, of which I am not sure if the first two are expected:
image

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.

Mark Device::getDPI() method as deprecated

2 participants