Picking: Declare working space in HitData
position
#17844
Labels
A-Picking
Pointing at and selecting objects of all sorts
C-Docs
An addition or correction to our documentation
C-Usability
A targeted quality-of-life change that makes Bevy easier to use
S-Ready-For-Implementation
This issue is ready for an implementation PR. Go for it!
What problem does this solve or what need does it fill?
Currently the returned
position
field inHitData
is space-ambiguous, leading users down a docs rabbit hole as they need to discern what backend is being used, then access that backend's docs to learn what space the position data is in.What solution would you like?
Something similar to
Projection
's variant solution, likeThis could extend to a better all-round solution, perhaps allowing
normal
data to be only included where necessary, e.g.(of course this is a rough outline, above code snippets are nonsense together but I hope you get the idea :) )
What alternative(s) have you considered?
Additional context
Inspired by @notmd's musings on the subject here
Related: #17681
The text was updated successfully, but these errors were encountered: