So ... curious ... runAsync provides a callback to let you know when its done doing its thing. Why aren't you just using that to know when you can mess with the objects you have created? To me, that is the bug, not anything in particular to do with what order GWT runs things asynchronously.
-Ben On Feb 16, 10:13 pm, Sky <[email protected]> wrote: > I created a GWT issue for this > here:http://code.google.com/p/google-web-toolkit/issues/detail?id=6036 -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
