[Walter Stovall]

Problem:
There’s a window on the screen that misbehaves in response to an event such as a button press but the application is very large and unfamiliar and you don’t know what class handles events dispatched to the window. It’s not a modal dialog so simply pausing the program and inspecting the AWT callstack can’t identify the window.

Is there an easy solution?

In an ideal world I’d have a debugging tool that would let me identify the window and break into the debugger when an event is dispatched to it.

[Riyad Kalla]

Interesting question… one thing you could try is to set a breakpoint in the EventDispatchThread’s event processing method, then go back to your window, and click the faulty button,it should break in the EDT and you could look at the call stack.

Although I’ve never done this, just the first thing taht popped in my head.

[Author]

Posts