Skip to content

Conversation

@HeikoKlare
Copy link
Contributor

This increase precision of size computation by reducing the number of pixel/point conversions. In particular, the minimumSize() method unnecessarily calculated in pixels even though all relevant values are in points. Inside the computeSizeInPixels() methods, several conversions were done as most other called methods operate on point values.

I was not able to demonstrate benefits of the higher precision yet, but it anyway cleans up the code by removing unnecessary conversions.

@github-actions
Copy link
Contributor

github-actions bot commented Oct 30, 2025

Test Results

  118 files  + 3    118 suites  +3   15m 0s ⏱️ + 3m 59s
4 650 tests +37  4 633 ✅ +36  17 💤 +1  0 ❌ ±0 
  330 runs  +18    326 ✅ +17   4 💤 +1  0 ❌ ±0 

Results for commit 918b82c. ± Comparison against base commit 4722846.

♻️ This comment has been updated with latest results.

@HeikoKlare HeikoKlare marked this pull request as ready for review October 30, 2025 18:45
This increase precision of size computation by reducing the number of
pixel/point conversions. In particular, the minimumSize() method
unnecessarily calculated in pixels even though all relevant values are
in points. Inside the computeSizeInPixels() methods, several conversions
were done as most other called methods operate on point values.
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.

Unnecessary pixel/point conversions in size computations

1 participant