I will try to create a standalone test case tomorrow. I tracked the issue down to the thisContainer.repaint(); call into the MorphAnimation updateState() function (If I commant this repaint, I do not see the component animation occur, of course, but the underlying layeredPane do not dissapear during the laps time of the animation) so I guess it has something to do with layeredPanes actually beeing on different branches of the components hierarchy (when a container is repainted, there is a recursive repaint call on its parents but has layered panes are not directly parents of one another, this might be the issue.) I'm too tired to analyze this correctly now though so I will have a look tomorrow ;)
On Thursday, September 27, 2018 at 6:21:32 AM UTC+2, Shai Almog wrote: > There are some edge cases in the paint order of overlays. If you can > isolate this into a standalone test case we can debug it. > -- 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/7df02e00-8c1b-41dc-bd5c-fe85f62cb5e3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
