Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!sun-barr!apple!motcsd!hpda!hpcuhb!hpindda!eav
From: eav@hpindda.HP.COM (Eugene Veteska)
Newsgroups: comp.windows.ms
Subject: Re: Re: Large dialog boxes eating memory (use CS_SAVEBITS)
Message-ID: <40130008@hpindda.HP.COM>
Date: 1 Dec 89 18:25:40 GMT
References: <40130007@hpindda.HP.COM>
Organization: HP Information Networks, Cupertino, CA
Lines: 29

/ hpindda:comp.windows.ms / paulkle@microsoft.UUCP (Paul Klemond) /  8:47 am  Nov 29, 1989 /
In article <40130007@hpindda.HP.COM> eav@hpindda.HP.COM (Eugene Veteska) writes:
>Hi,
>   I'm having problems with creating a big dialog box. If I create a big enough
>dialog box, when the box is displayed, most of my conventional memory is
>eaten up...
> ...As soon as the dialog is moved, the conventional memory comes back...
> I can't seem to figure out why this occurs.
>
>Eugene Veteska
>HP Information Networks Division
>eav@hpindda.hp.com

If YOU were writing a windowing package, what would you want to do when you
brought a window, especially a "temporary" window like a dialog, up in front
of one or more other windows? More importantly, what would you want to do
AFTER the window you had brought up went away? Take a look at "CS_SAVEBITS"
in the WNDCLASS window class description. This is kind of vague, I know, but
the answer lies there. One problem is that this is specified for windows for
which Windows saves the maps of, not for the dialog coming to the fore.
I'm a little surprised that, if you are correct, the implementation of this
doesn't keep the maps at a lower priority for when there is contention for
memory. It makes sense for Windows to free them when you move the dialog,
but it should free them when you want to open another dialog or window too.
That's speaking strictly as a "fellow developer", I haven't looked any of this
up in the Windows source...

Paul Klemond      paulkle@microsoft      uunet!microsoft!paulkle     Hi, Phil.
----------