Ok, I'm going to try seeing what a WC_Closebutton at the first level of the window does. I just tried Parenting to the first level and setting Visible=false and an unintended feature is that you can close and open the browser window and the browser is still exactly as you left it.
I just wonder if this is more taxing memory-wise than a normal close button. I only hear my hard drive loading up the Mozilla DLLs the first time I open up the browser.
|