Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!brutus.cs.uiuc.edu!apple!rutgers!att!chinet!patrickd
From: patrickd@chinet.chi.il.us (Patrick Deupree)
Newsgroups: comp.windows.ms
Subject: Re: Large dialog boxes eating memory
Message-ID: <1989Nov27.132326.1158@chinet.chi.il.us>
Date: 27 Nov 89 13:23:26 GMT
References: <40130007@hpindda.HP.COM>
Reply-To: patrickd@chinet.chi.il.us (Patrick Deupree)
Organization: Chinet - Chicago Public Access UNIX
Lines: 20

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.  I have no controls inside the box.  As soon as the dialog box
>is moved, the conventional memory comes back to normal.

We had a customer with this problem a while ago.  It seems (if I remember
correctly) that Windows treats that dialog box like a bitmap (in some way)
and retains the bitmap in memory.  When the dialog box is moved, the bitmap
is discarded and you have no more problems.  I don't remember what exact
conditions cause this to happen, but the only solution that our customer came
up with was to move the dialog box (as you found).  It's kind of a wierd
effect since their dialog box will come up and shift over a pixel, but you
gotta do what you gotta do.
-- 
"I place my faith in fools.  Self confidence, my friends call it."
					-Edgar Allen Poe

Patrick Deupree -> patrickd@chinet.chi.il.us