Fix InputEventArgs.Timestamp field #7910
Merged
Conversation
This file contains hidden or 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
|
I would think it is a good practice to keep the changes to minimum. This could be a PR of one word deleted, but it is full of changes unrelated to the issue. It renames private fields which was not discussed. Not sure why comments need to be deleted. |
|
Have updated this PR, apologies for the delay |
c985e66 to
04177af
Compare
pchaurasia14
approved these changes
Jun 28, 2023
|
@hughbe thanks for bringing the issue and for providing the fix as well. Thanks for your continued support to WPF. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fixes #7887
InputEventArgs.Timestampfield should not be static.Microsoft Reviewers: Open in CodeFlow