Re: local to screen
- From: Jamie <jamie_ka1lpa_not_valid_after_ka1lpa_@xxxxxxxxxxx>
- Date: Sun, 24 Dec 2006 16:22:47 -0500
Maarten Wiltink wrote:
"Jamie" <jamie_ka1lpa_not_valid_after_ka1lpa_@xxxxxxxxxxx> wrote in messageexcuse me!
news:Vvwjh.401$Yz7.322@xxxxxxxxxxxxxxx
[...]
The Vcl is just a simple wrapper for API calls in windows ...
It most certainly is not. That's the Windows unit.
The VCL is a class library that organises wrapper classes, original
controls, and supporting classes into a consistent hierarchy that
was very much not inherent in the original WinAPI calls and Windows
messages.
Groetjes,
Maarten Wiltink
The VCL are wrappers for Windows API's
how they are organize makes no differences, at the end, anything
that requires your PC to display, accept input, access hardware requires
you to call API's.
The VCL is just a pile of over head that simply ends up communicating
with the API system.
The term wrapper has nothing to do with what type of code is being used to perform this. It simply means the API code that is being used
in the background is not forcing the coder to deal directly with it and
most likely is aiding in it's use of it.
--
"I'm never wrong, once i thought i was, but was mistaken"
Real Programmers Do things like this.
http://webpages.charter.net/jamie_5
.
- Follow-Ups:
- Re: local to screen
- From: Maarten Wiltink
- Re: local to screen
- From: J French
- Re: local to screen
- References:
- local to screen
- From: VCLfreak
- Re: local to screen
- From: J French
- Re: local to screen
- From: VCLfreak
- Re: local to screen
- From: Jamie
- Re: local to screen
- From: Maarten Wiltink
- local to screen
- Prev by Date: Re: local to screen
- Next by Date: getting an event handler from a active-x dll dispinterface
- Previous by thread: Re: local to screen
- Next by thread: Re: local to screen
- Index(es):
Relevant Pages
|