Quote:
Originally Posted by Othesus
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.
|
That's what I meant, just setting visible=false keeps the window active and thus using resources.
The windows are loaded from disk the first time you open them in game. Afterwards they stay in memory even after you close them. However, the engine keeps two copies of it, a copy of the file on disk (in the root tree) and a copy of the active window you are seeing (in the root._HUD tree). Closing the window resets that second copy. Logging to char select also resets the entire active tree but keeps the other tree. However, you can also script changes to that one to make changes persistent over different characters (it's not written to disk however).
Whether that also applies to the Mozilla DLLs as well (which I doubt) or whether you just don't hear your hard drive because your operating system kept those DLLs cached in memory I cannot answer.