I stay strong in my opinion that getting package to work on most common
types of hardware is software vendor's responsibilty. Especially when it is
the only vendor who has the problem.
No explanations can change the fact that, if Delphi developer goes and buys
PC or laptop tomorrow, he/she will
recipients of list delphi
Subject: Re: [DUG]: Component Icons (again)
OK.
1. am unable to lower acceleration below 60Hz
2. already have the latest (and best?) driver
3. what is direct x5 and where do I get it (if I don't
already have it)?
4. are the any Delphi-side fixes that I can apply
On 12/04/2000 08:23:10, Mark Howard blurted out...
OK.
1. am unable to lower acceleration below 60Hz
trust me, you dont want to. :) developing at less than 1024x768 @ 75hz is not
something I'd recommend to anyone.
2. already have the latest (and best?) driver
quite sure?
3. what is
AFAIK it's an issue with how the driver handles. or rather doesn't handle
directx.
That's why lowering hardware acceleration also fixes it. Some Video cards
(S3 VIRGE notably) need new firmware, new drivers and directx 5 installed.
Max
Hello
The problem is with a new installation of D3 on a
OK.
1. am unable to lower acceleration below 60Hz
2. already have the latest (and best?) driver
3. what is direct x5 and where do I get it (if I don't already have it)?
4. are the any Delphi-side fixes that I can apply. eg if I don't use
components on the Internet or ActiveX pages, is there any
Nic Wise wrote:
2. already have the latest (and best?) driver
quite sure?
Absolutely - the version was added to the Web site early this month.
4. are the any Delphi-side fixes that I can apply. eg if I don't use
components on the Internet or ActiveX pages, is there any point in
-
From: Mark Howard [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, 12 April 2000 8:23 a.m.
To: Multiple recipients of list delphi
Subject: Re: [DUG]: Component Icons (again)
OK.
1. am unable to lower acceleration below 60Hz
2. already have the latest (and best?) driver
3. what
install Delphi, luckily
it worked.
Alex
- Original Message -
From: "Mark Howard" [EMAIL PROTECTED]
To: "Multiple recipients of list delphi" [EMAIL PROTECTED]
Sent: Tuesday, 11 April, 2000 2:25 PM
Subject: Re: [DUG]: Component Icons (again)
OK
Can anyone confirm
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
Could not restrain myself from making another note on how reduculas this
problem is and how shameful Borland should feel about it.
WHY? The problem is a known one - has been known since Delphi 3 or 4, and is
known to be a problem with a) faulty display drivers and/or b) non-current
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
Nic Wise wrote:
Of course I may get recommended here to use one computer and just try
several video cards. Done that , it costs money, depending on how
many cards
one tries, but finally it fixes the icons.
Not that easy with laptops videcards swaps. That is why when I
was
The length of replies from Max and the number of the others on the topic we
have seen before (about a hundred by now ?) clearly convince me that there
is no problem with IDE. It is just all other silly packages displaying their
icons in a wrong way, as we can see them well on any pc/laptop/card.
: 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
Hellooo! If you read my original post on this you will see that
the Dell is
installed with this "decent video card" (NeoMagic) and the very
latest driver.
I am NOT loading up any more component images than are provided
with a vanilla
install of D3 Prof.
So where does the problem lie??
Alex Kouznetsov spoke thusly at me:
To Max the educating man
I am glad you have time to learn about things such as why
Borland icons do not show up properly. Perhaps it is a
usefull knowledge for some people. I personaly prefer to
spend my working time on pure application development,
Leigh Wanstead
- Original Message -
From: Max Nilson [EMAIL PROTECTED]
To: Multiple recipients of list delphi [EMAIL PROTECTED]
Sent: Wednesday, April 12, 2000 02:54
Subject: RE: [DUG]: Component Icons (again)
Alex Kouznetsov spoke thusly at me:
To Max the educating man
I am glad
Hello
The problem is with a new installation of D3 on a new computer.
A goog number of the component icons are either black or
incorrectly displayed.
I had this problem a couple of weeks ago on another machine and
fixed it by downloading a newer video driver. Trouble is that
this machine (Dell
21 matches
Mail list logo
