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
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: