-
-
Notifications
You must be signed in to change notification settings - Fork 3.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
Move cursor position to internal state #7988
Conversation
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? |
I like this solution more than making |
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.
I agree, this seems like a much more appropriate approach to this.
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.
Agreed, this is very reasonable.
Removing controversial: we have strong consensus here (at least so far) and the impact is extremely scoped.
@james7132 I'm not sure this is even a breaking change as it has the same api surface I believe. Since you couldn't access the cursor position directly, only through |
Oh yeah you're right. Whoops. |
Objective
Fixes #7941
Setting cursor position on initialization probably isn't wanted anyways, but this does hurt discoverability because it moves cursor position to the
Window
api level. But I think this is overall a win in terms of usability.Solution
Move cursor position to internal window state so we can use ..default() in Cursor
Changelog