On 6/21/05, Andreas Raab andreas.raab@gmx.de wrote:
Switch to TestRunnerPlus (part of ToolBuilder examples). Or more accurately: Switch to any TestRunner which does not run tests in concurrent processes, thereby creating unforeseen interactions with the primary UI process, thereby at some point having multiple UI processes running thereby screwing up the display. It's amazing to me how people can deal with the default TestRunner at all given how flawed it is.
Yes, ok - but what about when I do want to raise a debugger from a non-UI process? Is there some safe, accepted way to do that?
Avi