These animations are meant to be much faster to hide some of those things. What's happening is two layout animations running in parallel without knowledge of each other and the second one essentially drops all its frames as it expired.
What's happening is this: - We get an event of leaving the text field so we initiate a layout animation which starts immediately - We get a second event of a new animation so we start that animation immediately but it's stuck in a queue behind the layout animation - By the time the second animation gets to run it expired A workaround would be to flush the animation queue before beginning an animation but it might make field transitions slower and I'm not sure that's what users want. -- 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/d9f592d0-0d04-4ee9-a7a9-74c383cbc3db%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
