mirror of
https://github.com/bevyengine/bevy
synced 2024-11-22 20:53:53 +00:00
fc07557913
# Objective - Make people stop believing that commands are applied immediately (hopefully). - Close #5913. - Alternative to #5930. ## Solution I added the clause “to perform impactful changes to the `World`” to the first line to subliminally help the reader accept the fact that some operations cannot be performed immediately without messing up everything. Then I explicitely said that applying a command requires exclusive `World` access, and finally I proceeded to show when these commands are automatically applied. I also added a brief paragraph about how commands can be applied manually, if they want. --- ### Further possibilities If you agree, we can also change the text of the method documentation (in a separate PR) to stress about enqueueing an action instead of just performing it. For example, in `Commands::spawn`: > Creates a new `Entity` would be changed to something like: > Issues a `Command` to spawn a new `Entity` This may even have a greater effect, since when typing in an IDE, the docs of the method pop up and the programmer can read them on the fly. |
||
|---|---|---|
| .. | ||
| bevy_animation | ||
| bevy_app | ||
| bevy_asset | ||
| bevy_audio | ||
| bevy_core | ||
| bevy_core_pipeline | ||
| bevy_derive | ||
| bevy_diagnostic | ||
| bevy_dylib | ||
| bevy_dynamic_plugin | ||
| bevy_ecs | ||
| bevy_ecs_compile_fail_tests | ||
| bevy_encase_derive | ||
| bevy_gilrs | ||
| bevy_gltf | ||
| bevy_hierarchy | ||
| bevy_input | ||
| bevy_internal | ||
| bevy_log | ||
| bevy_macro_utils | ||
| bevy_math | ||
| bevy_mikktspace | ||
| bevy_pbr | ||
| bevy_ptr | ||
| bevy_reflect | ||
| bevy_render | ||
| bevy_scene | ||
| bevy_sprite | ||
| bevy_tasks | ||
| bevy_text | ||
| bevy_time | ||
| bevy_transform | ||
| bevy_ui | ||
| bevy_utils | ||
| bevy_window | ||
| bevy_winit | ||