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.
You aren't understanding the issue properly. The callback method you just
mentioned is the onSuccess() method that you override. The issue is when
that method is being called. In production the onSuccess() method is
actually being deferred (the word I should have been using) until after
the
Fair point, Ben.
The onSuccess() method is where we are creating the async objects and no
other code *should* be interacting with those objects elsewhere.
However, other objects that needed to exist on page load, long before async
code gets loaded, do need to interact with objects that are
Again, you can probably argue that a better design would have it so that the
already existing objects should be waiting for the async objects to inform
them of their creation. Ultimately you are still checking for null and
designing it that way it's obvious that you have to check for null. But
I have two bugs that just cropped up but they only occur in production
and not in development mode.
One is an actual javascript error so I'll probably be able to figure
that one out without debugging, though it might be painful.
One does not give a javascript error but is a functionality problem
Forgot to say I'm using AppEngine version 1.4.2 and GWT 2.2.0,
developing on Eclipse 3.5.2. Production is running on google's
appengine.
On Feb 16, 10:28 am, Sky myonceinalifet...@gmail.com wrote:
I have two bugs that just cropped up but they only occur in production
and not in development
Ok, I actually figured out exactly what's causing production to run
differently than dev.
The problem is that GWT.runAsync() is behaving differently in dev
mode.
It's not actually running out of sync of the rest of the code. In
production, even if the code behind GWT.runAsync() has already been
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 google-web-toolkit@googlegroups.com.
To unsubscribe
