-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
Unify Cursor and Pointer nomenclature #19688
Copy link
Copy link
Closed
Labels
A-InputPlayer input via keyboard, mouse, gamepad, and morePlayer input via keyboard, mouse, gamepad, and moreA-PickingPointing at and selecting objects of all sortsPointing at and selecting objects of all sortsA-WindowingPlatform-agnostic interface layer to run your app inPlatform-agnostic interface layer to run your app inC-FeatureA new feature, making something new possibleA new feature, making something new possibleC-UsabilityA targeted quality-of-life change that makes Bevy easier to useA targeted quality-of-life change that makes Bevy easier to useS-Needs-DesignThis issue requires design work to think about how it would best be accomplishedThis issue requires design work to think about how it would best be accomplished
Description
Metadata
Metadata
Assignees
Labels
A-InputPlayer input via keyboard, mouse, gamepad, and morePlayer input via keyboard, mouse, gamepad, and moreA-PickingPointing at and selecting objects of all sortsPointing at and selecting objects of all sortsA-WindowingPlatform-agnostic interface layer to run your app inPlatform-agnostic interface layer to run your app inC-FeatureA new feature, making something new possibleA new feature, making something new possibleC-UsabilityA targeted quality-of-life change that makes Bevy easier to useA targeted quality-of-life change that makes Bevy easier to useS-Needs-DesignThis issue requires design work to think about how it would best be accomplishedThis issue requires design work to think about how it would best be accomplished
Type
Fields
Give feedbackNo fields configured for issues without a type.
What problem does this solve or what need does it fill?
Picking talks about
Pointers,Windowtalks aboutCursors. Shouldn't they use the same terminology?What solution would you like?
Pick one or the other. Or a secret third option!
What alternative(s) have you considered?
Leave it as-is
Additional context
Brought up by @ickshonpe in #19668 (comment)