Re: window namespace in super-dev-mode

Nevermind... It seems to be solved already...

https://gwt.googlesource.com/gwt.git/+/7ed2e49921fb67ac4998186a7b33f421d2b42729

Am Montag, 31. März 2014 09:34:50 UTC+2 schrieb Klemens Schrage:

Hello,

I'm experiencing some problems when debugging (especially) static methods in super-dev-mode in Chrome. When I have inspected / unfolded the this-node in the scope variables view on a previous breakpoint the devtools-window begins to hang when entering a breakpoint in a static method. Chrome automatically unfolds the static method's this-node which seems to be the window-node. The scope variables view is filled with a huge number (all?) of functions. Obviously too much for the devtools. 

Would it be possible to enclose those methods in an additional subnode / container variable to avoid the performance problem? Besides the problem for static methods it would also help with "normal" inspecting the window namespace. Correct me if I'm wrong, but one doesn't need those functions for debugging purposes.

Best regards

Klemens Schrage

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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 http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.