Listen for the remove event and then set isInitialApplicationSetup=false.
Hmm the problem occurs as the component is hearing other components that are being removed form the same parent canvas.
Use the event target to determine which component is being removed.
Hmm that event seems to be restricted to the current component, but for that
component, it dispatches the event 6 times with the following targets.
From the small amount of information, it's difficullt to know exactly what you are trying to
do and where. Sounds like you are listening to the wrong event or the right event from the wrong component!
If you are relying on the order of event processing, there's most likely a flaw in your design.
Its a very complex user interface unfortunately and would take a long time
to explain. thx anyway
Its not a Bug Its a Feature
Bubbling is at its best,
you can alway stop event bubbling with stopPropogation() if you want inside your listener , but best bet is to only
use currentTarget property instead of target.