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 a lot of the code written might not have been planned for something to be created asynchronously and so it just assumes it was created earlier. But when the createPage() method is changed to have a GWT.runAsync() inside it, that suddenly changes things and introduces this problem.
We just need dev mode to behave correctly so us developers can realize we either need to check for null or change our design. Sorry I wasn't able to say that more concisely. -- 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.
