-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Add window entity to TouchInput events #11128
Conversation
Welcome, new contributor! Please make sure you've read our contributing guide and we look forward to reviewing your pull request shortly ✨ |
It looks like your PR is a breaking change, but you didn't provide a migration guide. Could you add some context on what users should update when this change get released in a new version of Bevy? |
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.
Other than fixing compile errors, it looks good!
25a7ff3
to
3bee1fc
Compare
Fixed those tests, sorry about that. I wonder if it would also be a good idea to make |
Not sure about that one, but I believe this would deserve another PR. |
Definitely another PR. I kind of like the idea though 🤔 |
I believe this would fix #6011 . |
Merging. If this fails, please merge |
Head branch was pushed to by a user without write access
Rebased onto main to fix CI issues and force pushed. Looks like you might need to add this back to the queue. |
Done, thank you :) |
Objective
If you have multiple windows, there is no way to determine which window a
TouchInput
event applies to. This fixes that.Solution
TouchInput
, just like the other input events.Migration Guide
window
field when constructing or destructuring aTouchInput
struct.