[Suggestion] Two stage initialization

Hello again, I bet your sick of my suggestions by this point 😄

Unity’s MonoBehaviors have an Awake and Start method, Awake is always called in all scripts before Start, this allows two stages of initialization which makes scripts less dependent on execution order. Scripts with dependencies on other started scripts can use Start to ensure they have already called their Awake code.

One thing I’ve noticed is that Entitas’ initializing systems are very dependent on order. I think more flexibility could be introduced by have two initialization methods, one that is guaranteed to run after the previous initialization method is run on all systems.

Thoughts?

[mzaks]

You see that this happens because your systems suppose to do more than one thing 😜

[JamesMcMahon]

The use case would be that if System A creates a entity on init that B is listening to. You could reorder them, but what if B creates an entity that A is listening to.

With the two stage system A and B could register their listeners and in the second stage create their entities.

If SetPool was called again when reseting Entitas it could be used as the first stage, since it’s called before initialize.