Skip to content

Conversation

@HeikoKlare
Copy link
Contributor

The handling of different autoscaling modes is currently spread across the DPIUtil class, based on String matching and system property retrieval.
This change extracts and AutoScale class that encapsulates functionality and information related to a specific autoscaling mode (string representation, conversion, compatibility to monitor-specific scaling) into a dedicated class.

This is particularly a preparation for changing the default mode on Windows to quarter/monitor-specific scaling, as adapting the String matching logic for that would become incomprehensive.

@HeikoKlare HeikoKlare force-pushed the formalize-autoscale branch 3 times, most recently from 19052cc to 0ad9f13 Compare January 16, 2026 11:18
@github-actions
Copy link
Contributor

github-actions bot commented Jan 16, 2026

Test Results

  176 files    176 suites   26m 53s ⏱️
4 680 tests 4 658 ✅ 22 💤 0 ❌
  485 runs    479 ✅  6 💤 0 ❌

Results for commit e9dc9dd.

♻️ This comment has been updated with latest results.

The handling of different autoscaling modes is currently spread across
the DPIUtil class, based on String matching and system property
retrieval.
This change extracts and AutoScale class that encapsulates functionality
and information related to a specific autoscaling mode (string
representation, conversion, compatibility to monitor-specific scaling)
into a dedicated class.

This is particularly a preparation for changing the default mode on
Windows to quarter/monitor-specific scaling, as adapting the String
matching logic for that would become incomprehensive.
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.

1 participant