Re: Type Corruption migrating from GWT 2.6.1 => 2.7.0

Just a shot in the dark.

maybe you changed the linker ? IIRC the default changed around 2.7.

Good luck. 

   A. 

On Thu, Jul 6, 2017 at 11:59 AM <bobbitdiddle@gmail.com> wrote:

OK, it looks like we have two "apps" each with its own entry point, but they share the content of $wnd, which contains a JS Framework.  So the problem is that JS calls can enter either "app" and each "app" appears to be have it's own frame (So $wnd.frames is an array of two windows.)

As mentioned, the problem is that because because both "apps" are plugged into the JS Framework, one might see a GWT object created by the other, but type comparison of objects created in one "app" fails in the other.  This worked in SGWT 2.6.1, but doesn't in GWT 2.7.0.

Does that provide enough detail to answer the question?  Has handling of multiple apps (or "entry points") for a single browser window changed in GWT 2.7.0, specifically with respect to type comparison?

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.