Global Gizmos

[atlv24]

Objective

• use gizmos in non-system contexts, such as deep in a math library or callback without ecs access.
• kind of upstream https://github.com/atlv24/glizmo
• builds off of Make it possible to statically construct gizmo buffers #22105

Solution

• mutex + deref

Testing

[janhohenheim]

Great idea :)

[janhohenheim]

nit: we usually call the thing that creates gizmos Gizmos in plural, so you may want to rename this to gizmos()

[atlv24]

my reasoning for singular was that i was designing the api to discourage holding this as an object to get multiple gizmos out of, so i called it gizmo and made it return a hard-to-name type intentionally

[NicoZweifel]

Nice, works! I already see use cases for this.

I am wondering about situations where a calculation only happens occasionally and I want to draw persistent gizmos until the next calculation. Is there an easy way to do this without using a new component or resource to track the state or do I always have to call gizmo every frame?

Approving since it works and the above behavior is achievable with a bit of extra code (or std gizmos), so no need to resolve the comment to merge.

[atlv24]

@NicoZweifel ive been thinking about this, I have a solution in mind but its gonna be more code and more complicated. I want to land this first