I don't recall ever using setComponentLimit so it might have been something that was implemented and never tested properly. Looking at the code it seems we remove the components from the top but don't scroll up by the right amount to compensate which might be an issue. I'm not sure if this is fixable without an API change.
Either way you should open an issue on this. -- 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 codenameone-discussions+unsubscr...@googlegroups.com. 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/de58a6b1-7dfa-4c27-8c44-c346b23ba9e0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
