<snip>
> Ah but... a lot of VCL stuff is dependent on DLL calls into
> the Win32 API.
> The Comctl32 thing broke the Delphi TImageList component a
> few years back.
> Those DLLs are changing all the time. All that you have bound
> up into your app is the Delphi code that calls those APIs. The APIs
can
> and do change all the time. Have a look at Windows.pas and you will
find it
> consists mostly of calls to external DLLs, there is very little actual
Delphi
> code in there.
Unless MS are trying to break code (including there own), then they try
not to change the Win API, (yeah I know they do anyway).
I have worked on simple VB apps that just don't work because the
developer machine has a slightly different version of a mapping or grid
OCX to that installed on a client.
Of course the problem is made worse in that OCX's designed for VB tend
to be fat (compared with VCL), have no source availible and even if you
did have source most OCX's are written in C++. Which reminds me - if VB
is so good how many MS apps are written in VB? I suspect Borland use
Delphi in house more than MS would use VB...
---------------------------------------------------------------------------
New Zealand Delphi Users group - Offtopic List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
