[WiP] Change monitor-specific scaling setting before Display creation #1716
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The method
Display#setRescalingAtRuntime()
allows to activate the monitor-specific scaling mechanism on Windows. This must, however, actually be activated before the Display is instantiated, like it is done during the Display constructor execution if the VM argument for global activation of monitor-specific scaling is specified. In consequence, calling#setRescalingAtRuntime()
does not take the full intended effect.This change deprecated the method (along with its according accessor
#isRescalingAtRuntime()
) and adds a new method to activate monitor-specific scaling on the Display class instead of an instance to be used for subsequent displays to be instantiated.