Dragan --

Thanks for the sample code. That's more or less what I was looking at already.

In my teensy bit of testing so far, however, it may not be enough. For one thing, "close debugger" in code doesn't always close the debugger! ... apparently it doesn't do anything if the debugger is not idle. (I think that's it).

And, calling "Debug" sets the focus on the debugger ... not what you expect if you've clicked someplace else.

And, a typical session involves clicking back and forth between the form you are editing and PEM Editor. I'm sure it would be most annoying if the debugger kept flashing back and forth each time you did so.

I'll be trying this more over the next few days (probably a weekend thing, now that I think of it), but am not convinced there's a workable solution.

BTW, my statement about the Trace Window was premature -- all the debuggers windows cause speed degradation, some are just much worse than others.



>>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.
>
>On activate,
>
>this.lDebuggerOn=wvisible("trace")
>if this.lDebuggerOn
> close debugger
>endif
>
>on deactivate
>
>if this.lDebuggerOn
> debug
>endif
>
>May just work.