Fix for Track not arranging after IsDirectionReversed property changed. #12575
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@dotnet-policy-service agree company="Actipro Software LLC" |
|
You can test this PR using the following package version. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does the pull request do?
Fixes the Track control not arranging after IsDirectionReversed property is changed.
What is the current behavior?
The control doesn't update its appearance until it is resized after that property changes.
What is the updated/expected behavior with this PR?
That the control updates immediately when the property changes.
How was the solution implemented (if it's not obvious)?
Added to IsDirectionReversedProperty to AffectsArrange.
Checklist
(Not applicable)
Breaking changes
None.
Obsoletions / Deprecations
None.
Fixed issues
None.