Naomi --

The problem here doesn't have to do with whether the debugger is visible, rather that when it is open it degrades performance on PEM Editor is much that it could be considered unusable.

Thus, the suggestion to close the debugger windows on activation of PEMEditor, re-showing them on deactivation.

No idea yet how that would feel as a user, with the debugger coming and going.

>Alternatively you can move the debugger window out of the screen (though I don't know if it would help, I didn't follow the whole thread)
>
>>It turns out that the trace window is the worst culprit -- but they all contribute.
>>
>>So the proposed solution would have to be do hide all of them (on activation) and them show them again (on deactivation).
>>
>>It looks like two ugly choices:
>> (1) performance so slow that you won't use it.
>> (2) having the debugger and its windows coming and going each time you activate / deactivate it.
>>
>>Truly too bad there's no way to turn off the debugger without closing it.
>>
>>>am investigating that very point.
>>>
>>>>>>Actually, the problem with PEM Editor and the debugger really has to do with the trace window in the debugger. PEM editor is just a form with a timer, actually, and the performance for any form degrades if you have the trace window open. That can't be helped (and, believe me, we've spent some time trying).
>>>>>
>>>>>Just a thought here -- if the trace window is the culprit for the slowness of the form, could the trace window be closed automatically on the activate event method and then reopened (if closed) on the deactivate event method of the PEM Editor form?
>>>>
>>>>

>>>>HIDE WINDOW trace
>>>>...
>>>>SHOW WINDOW trace
>>>>

>>>>
>>>>May do the trick.