Kanabenki 312df3cec7 Use warn_once where relevant instead of manually implementing a single warn check (#11693) ... # Objective - Some places manually use a `bool` /`AtomicBool` to warn once. ## Solution - Use the `warn_once` macro which internally creates an `AtomicBool`. Downside: in some case the warning state would have been reset after recreating the struct carrying the warn state, whereas now it will always warn only once per program run (For example, if all `MeshPipeline`s are dropped or the `World` is recreated for `Local<bool>`/ a `bool` resource, which shouldn't happen over the course of a standard `App` run). --- ## Changelog ### Removed - `FontAtlasWarning` has been removed, but the corresponding warning is still emitted.		2024-02-05 21:05:43 +00:00
..
button.rs	bevy_reflect: FromReflect Ergonomics Implementation (#6056)	2023-06-29 01:31:34 +00:00
image.rs	Feature-gate all references to bevy_text in bevy_ui (#11391)	2024-01-28 16:24:54 +00:00
label.rs	bevy_reflect: FromReflect Ergonomics Implementation (#6056)	2023-06-29 01:31:34 +00:00
mod.rs	Integrate AccessKit (#6874)	2023-03-01 22:45:04 +00:00
text.rs	Use warn_once where relevant instead of manually implementing a single warn check (#11693)	2024-02-05 21:05:43 +00:00