-
-
Notifications
You must be signed in to change notification settings - Fork 21.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarify behavior of InputEvent.is_match
and Shortcut.matches_event
#97106
Clarify behavior of InputEvent.is_match
and Shortcut.matches_event
#97106
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me
Once you've fixed the last detail from me please squash your commits into one, see here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The new description matches the implementation.
InputEvent.is_match
and Shortcut.matches_event
This comment was marked as resolved.
This comment was marked as resolved.
- Shortcut: Clarifies how matches_event() method compares events - InputEvent: Clarifies is_match() method does not consider event states
30a4c55
to
4f4fd1a
Compare
Thanks! And congrats for your first merged Godot contribution 🎉 |
Thank you! |
Fixes #97048