I managed to create what appeared to be an infinite loop by resizing the desktop
with an event monitoring such, which then triggered itself, etc. When this had
happened, I was unable to close the integrated browser, or EWB IDE at all. I had to
kill it. Not serious (I'll not create the loop again), but it might be nice to have
a way to kill the browser when this happens.

/Matthew Jones/

Matthew,

<< I managed to create what appeared to be an infinite loop by resizing the
desktop with an event monitoring such, which then triggered itself, etc.
When this had happened, I was unable to close the integrated browser, or EWB
IDE at all. I had to kill it. Not serious (I'll not create the loop again),
but it might be nice to have a way to kill the browser when this happens. >>

The browser is a COM object that runs in the main thread of the application
(it has to, it's a UI control), and there isn't any way to "take control" of
it once it stuffs up the main thread.

Tim Young
Elevate Software
www.elevatesoft.com

Ah well. It's the only time it has happened, and I knew what I'd done straight away.
Classic programming fault of course. EWB put me back where I was, so I didn't lose
anything at all.

/Matthew Jones/