Currently, it is not possible to create an mx effect that is capable of loading other effects due to message order. Dynamically created abstractions fire first when using the same [send]/[receive] as already existing abstractions. In a scenario, where a dynamically loaded abstraction creates other abstractions dynamically, we want the order of state saving messages to be top->down, not bottom->up, otherwise the children receive their state before they are created at state loading time.
In order for nested dynamic creation to work with state management, a mechanism to influence order is needed.
Currently, it is not possible to create an mx effect that is capable of loading other effects due to message order. Dynamically created abstractions fire first when using the same [send]/[receive] as already existing abstractions. In a scenario, where a dynamically loaded abstraction creates other abstractions dynamically, we want the order of state saving messages to be top->down, not bottom->up, otherwise the children receive their state before they are created at state loading time.
In order for nested dynamic creation to work with state management, a mechanism to influence order is needed.