Comments on: The infamous callLater()

By: Manfred Karrer

Manfred Karrer — Fri, 15 Jul 2011 16:18:35 +0000

our case was that a component has been cleaned up in a destroy method, and therefore some properties was set to null. but later an update displaylist was called again (caused from internal callLater) and the we got the nullpointer exception. we solved this issue with a boolean check if the component has been destroyed already. not very nice but it worked. we never used callLater in our client code. in situations when it was used by a developer to solve (hide) a tricky problem, it was always possible to solve the issue without callLater when investigating for the cause of the issue. but i know there are some situations where it is not easy…

By: Brandon Heyer

Brandon Heyer — Fri, 15 Jul 2011 15:41:37 +0000

You said you were receiving NPEs with custom components in the updateDisplayList. I am running into the same problem, while trying to update a components skin class and intemrenderer, if I do one or the other, everything works great, but when I do both, it causes issues. What was your non-callLater work around? Not because I wish to solely avoid using callLater, but with how my code would have to be written, it would lead to chained callLaters within a recursive function…

By: Arindam Biswas

Arindam Biswas — Thu, 07 Jul 2011 11:27:51 +0000

Didn’t know this. very helpful, one to bookmark.

By: Bernd

Bernd — Sun, 21 Jun 2009 14:50:23 +0000

thanks for your effort and for sharing this knowledge 😉