fix NumericUpDown Spinned event #18180
Merged
+2
−3
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
|
You can test this PR using the following package version. |
|
|
@cla-avalonia agree |
robloo
reviewed
Feb 13, 2025
|
You can test this PR using the following package version. |
maxkatz6
approved these changes
Feb 15, 2025
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?
For NumericUpDown control, raise Spinned event after value change.
What is the current behavior?
At the time of (NumericUpDown.)Spinned event the value is stale, not incremented / decremented yet.
What is the updated/expected behavior with this PR?
At the time of (NumericUpDown.)Spinned event the value is already incremented / decremented. So, subscribers will see correct current value.
Checklist
Breaking changes
Fixed issues