fix(iOSmacOS): Obsolete the use of readonly fields #9126
Merged
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.
GitHub Issue (If applicable): closes #9027
PR Type
What kind of change does this PR introduce?
What is the current behavior?
ViewHelper
has C#readonly
fields forMainScreenScale
andIsRetinaDisplay
that are evaluated only once. IOW they are set to the current screen when the evaluation is done and moving the window to a different screen will not update the values.What is the new behavior?
Both
readonly
fields are now decorated with[Obsolete]
attributes giving update instructions to directly use (now cached)DisplayInformation
properties. This ensure the current (screen) values will be given for every call during the app lifetime.PR Checklist
Please check if your PR fulfills the following requirements:
Screenshots Compare Test Run
results.Other information
Internal Issue (If applicable):