Skip to content

Move EntityCursor out of bevy_feathers #25250

Description

@viridia

What problem does this solve or what need does it fill?

The EntityCursor component has proven its usefulness, but right now it's only usable by feathers since that's where it lives. But the implementation is not at all feathers-specific, and could go in another crate.

What solution would you like?

Probably the best place to put it would be in bevy_picking.

@kfc35

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-PickingPointing at and selecting objects of all sortsA-UIGraphical user interfaces, styles, layouts, and widgetsC-FeatureA new feature, making something new possibleD-TrivialNice and easy! A great choice to get started with BevyM-Migration-GuideA breaking change to Bevy's public API that needs to be noted in a migration guideS-Needs-TriageThis issue needs to be labelled

    Type

    No type

    Projects

    Status
    Needs SME Triage

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions