-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
ui_material example should show how to use Globals #16829
Copy link
Copy link
Open
Labels
A-RenderingDrawing game state to the screenDrawing game state to the screenC-DocsAn addition or correction to our documentationAn addition or correction to our documentationC-ExamplesAn addition or correction to our examplesAn addition or correction to our examplesD-StraightforwardSimple bug fixes and API improvements, docs, test and examplesSimple bug fixes and API improvements, docs, test and examplesS-Ready-For-ImplementationThis issue is ready for an implementation PR. Go for it!This issue is ready for an implementation PR. Go for it!
Metadata
Metadata
Assignees
Labels
A-RenderingDrawing game state to the screenDrawing game state to the screenC-DocsAn addition or correction to our documentationAn addition or correction to our documentationC-ExamplesAn addition or correction to our examplesAn addition or correction to our examplesD-StraightforwardSimple bug fixes and API improvements, docs, test and examplesSimple bug fixes and API improvements, docs, test and examplesS-Ready-For-ImplementationThis issue is ready for an implementation PR. Go for it!This issue is ready for an implementation PR. Go for it!
How can Bevy's documentation be improved?
It's easy for a user to get tripped up by using the wrong globals import, e.g. from
bevy_pbr. We don't seem to show the correct import anywhere in our docs or examples.Something like
Seems to work, but I'm not 100% sure if this is the canonical way to do it.