Replies: 1 comment · 7 replies
-
|
Since you have mutable EDIT: Also, notice that when we're talking about removing or de-spawning, the order of hooks & observers is not the same, observers run before the hooks. |
Beta Was this translation helpful? Give feedback.
-
|
No I was expecting the commands from the hooks to run before the observers themselves as in : |
Beta Was this translation helpful? Give feedback.
-
|
Oh, I don't quite understand what you meant with |
Beta Was this translation helpful? Give feedback.
-
|
When a hook runs, the command queue might not be empty. When a command is encountered while running the hook, the standard behavior would have been to add that command at the end of the queue. Instead the choice has been made to make these commands jump to the front of the queue. That makes sense to me as you want all the hook logic to apply immediately. But I would have gone one step further and have these commands run before any observer as well. I was curious why this is not the case. I'm not sure why but I can't access your link. |
Beta Was this translation helpful? Give feedback.
-
|
Understood. The link leads to the Bevy Discord server, you can find an invitation in the Bevy Community page, you might not have a Discord account ? |
Beta Was this translation helpful? Give feedback.
-
|
I was missing the invitation. Thanks ! |
Beta Was this translation helpful? Give feedback.
-
I'm curious about the order things run when both a hook and an observer are scheduled to run, assuming both run commands and that the command queue is not empty. I found out the order was:
hook, observer, hook's commands, observer's commands, command queue
I thought since hooks are designed to maintain invariants, their commands would either be pushed to the end of the queue (and their use discouraged in that case) or that they would execute right after the hook itself but the observer runs in between. Is this correct ?
Beta Was this translation helpful? Give feedback.
All reactions