Good point Brandon. Also check out the more advanced conditionals you can use in the lower part of the breakpoint screen.
For example, for a more advanced algorithm, you might find yourself stepping along manually with F6 and hovering to check the variable values to find a specific condition. However, you could just set these conditions on the breakpoint (i.e. 5th iteration, foo is equal to the nth element of bar and bar.length is greater than 3. Now, as Ron Popeil says, "Just set it and forget it!" <https://lh6.googleusercontent.com/-HrXUE-5h6cc/T7mk-o1W7qI/AAAAAAAABv8/uqOieUY9E20/s1600/Selection_028.png> This makes debugging wicked easy. But also be aware that just using a blanked "NullPointerException" breakpoint will expose poorly written code (yours or libs) that has wrapped blocks with try/catches instead of doing null checks (i.e. in JAXB). Sincerely, Joseph -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/Ks74VoaX7sMJ. 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.
