-
-
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
Unify CursorIcon
management.
#14433
Labels
A-Windowing
Platform-agnostic interface layer to run your app in
C-Usability
A targeted quality-of-life change that makes Bevy easier to use
Comments
mintlu8
added
C-Feature
A new feature, making something new possible
S-Needs-Triage
This issue needs to be labelled
labels
Jul 22, 2024
mintlu8
changed the title
Centralized
Unify Jul 22, 2024
CursorIcon
management.CursorIcon
management.
alice-i-cecile
added
A-ECS
Entities, components, systems, and events
C-Usability
A targeted quality-of-life change that makes Bevy easier to use
A-Windowing
Platform-agnostic interface layer to run your app in
and removed
C-Feature
A new feature, making something new possible
S-Needs-Triage
This issue needs to be labelled
A-ECS
Entities, components, systems, and events
labels
Jul 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-Windowing
Platform-agnostic interface layer to run your app in
C-Usability
A targeted quality-of-life change that makes Bevy easier to use
What problem does this solve or what need does it fill?
Having multiple sources of
CursorIcon
management (likebevy_egui
) in a project can lead to confusing bugs.What solution would you like?
Have
CursorIcon
be reverted by bevy onFirst
based on a resource likeDefaultIcon
. "Backends" should only write to it if needed to minimize conflicts.What alternative(s) have you considered?
Keep things as is?
The text was updated successfully, but these errors were encountered: