Since my code is always golden (ya right!) and/or my memory is getting weak for remembering the names of all the classes involved, I often do not know how to find the source that is causing / exhibiting the problem.
Or I know of some UI within Eclipse or Jazz that has similar or desired behavior that I would like to emulate. Good old monkey see, monkey do.
A dumb or simple Eclipse debugger trick in case it ever might help you out:
- Launch a target Eclipse.
- Invoke the UI action to realize the wizard, dialog or editor.
- Pause the main thread of the target launch. If the code is not run on the main or UI thread, pause the VM while things are chugging away and find the interesting thread.
- Find the relevant stack frame and locate the interesting variables.
- Jump to the correct code to find the bug or the example you wish to emulate.
Hope this helps someone work faster and smarter.