Your definition of conflict isn't accurate. Conflict is far more complicated than most assume since layout and validation can break components in a different hierarchy.
That's why we introduced the animation manager. We also have ComponentAnimation.compoundAnimation() which allows you to run animations in parallel and handles the mutation portion (which has no visual implication) in sequence to prevent collision. -- You received this message because you are subscribed to the Google Groups "CodenameOne Discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/codenameone-discussions. To view this discussion on the web visit https://groups.google.com/d/msgid/codenameone-discussions/864917c1-5d93-497f-bbd4-9a10d2ce2202%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
