On Tue, Oct 4, 2011 at 6:37 PM, Jens <jens.nehlme...@gmail.com> wrote:
> You shouldn't use this solution. GWT.runAsync is used to create a code > split point and not to execute things asynchronously. I don't want to execute things asynchronously. I want to execute things * synchronously*. > As far as I know these code split points act synchronously in dev mode but > asynchronous in production/compiled mode. I think this is because in dev > mode there are no .js files (each code split point will result in a separate > .js file when you compile your app) that can be downloaded asynchronously > using GWT.runAsync. So in dev mode GWT.runAsync gets somehow (synchronously) > emulated. > > Do you really want to code split these single methods? > That's not I primary want to do but how can I achieve what I want to do? I want to be sure that *first()* is executed before *second()* and that second() is executed exactly when first() has finished its job. -- 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 from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
