bevyengine / bevyengine/bevy

Decouple `PointerId` and `PointerKind`

Open
#20,418 3 comments 3 reactions 0 assignees View on GitHub
A-Input A-Picking C-Feature
Dominant language
Rust
Stars
48.2k
Forks
4.8k
Avg merge
3d 22h
Merged PRs (30d)
161

Description

When making a custom ID'd pointer, it is also desired to be able to specify what *kind* of pointer it is, because application logic can change based on this. Today, these two are coupled.

Pointers do not use the Entity as an ID, because lifting the pointer despawns the entity, and the pointer being controlled needed a stable ID. It's possible we can solve this problem today, or just use a UUID under the hood for all pointers that is stable between pointers lifting.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.