On the same note of not being able to restrain myself, Alex Kouznetsov
grumbled:
Could not restrain myself from making another note on how reduculas this
problem is and how shameful Borland should feel about it.
In the final analysis the problem is Borland's as it is their product that
we are
Thanks Max - you put it a lot better (and with a lot more info) than I ever
could.
I can't see how its Borland 'problem' tho - when its a problem when anyone
is using large image lists on lousy hardware/drivers.
I imagine that the cache 'problem' is also why it is fixed when you drop the
Nic Wise commented:
Thanks Max - you put it a lot better (and with a lot more info)
than I ever could.
Purely a painful expriance and desire to educate others 8-)
I can't see how its Borland 'problem' tho - when its a problem
when anyone is using large image lists on lousy
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Max Nilson
Sent: Wednesday, 12 April 2000 12:23
To: Multiple recipients of list delphi
Subject: RE: [DUG]: Component Icons (again) [Long]
snip
Option 1: Check the ComCtl32.DLL version. Versions
: Wednesday, 12 April 2000 13:41
To: Multiple recipients of list delphi
Subject: RE: [DUG]: Component Icons (again) [Long]
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Max Nilson
Sent: Wednesday, 12 April 2000 12:23
To: Multiple recipients
Patrick Dunford asked:
When the Comctl32 updates came out originally there was a lot
of grumping because the imagelists in older Delphi programs
stopped working properly (or was that it - I'm dredging my
memory now) - don't remember the details too well but when IE4
shipped it broke the
