Subject Re: R: [IBO] Memproof errors (Repost)
Author Marco Menardi
Well, I don't have Win98 anymore, so I can't test personally. But
about 'laziness', did you try what I suggested you in a previous
post? I can't claim to be a IBO guru, but I'm enough 'expert' to make
my suggestions, expecially if no other solution is provided, worth a
try, please.
I paste my previous post here, for your greater convenience ;)
-----------
From: "Marco Menardi" <mmenaz@l...>
Date: Tue Sep 24, 2002 9:39 am
Subject: Re: Memproof errors (Repost)

As you can see in the "credit" section of the source, I've tried to
reduce memory leaks of that component, that was preventing me of
using my program in Win98. Since I moved to Win2000, I corrected the
code when also in Win2000 I had some problem, but since I'm not a Win
guru and, as far as I've read in Google, .Assign has changed from old
delphi version to new one, there is a lot of confusion about it's
usage.
Anyway, I've find that is good after and assign to use the following
code:
Buttons[i].Glyph.Assign( My_Glyph );
Buttons[i].Glyph.Dormant;
Buttons[i].Glyph.FreeImage;

so could you try to add the Dormand and FreeImage line when propriate
inside the SysStateChanged procedure? I think that eliminate resource
leaks is the better way to avoid "impossible" bugs later...
Let me (and the list) know
Thanks
Marco Menardi