Hi, Christian Andersen!
On 10 Apr 97  11:15:47 you wrote to Jerry Coffin
 CA> For me MFC was the natural RAD tool, not in spite of, but because, it
 CA> is a relatively thin wrapper around the API code. Almost everything I
 CA> know from API programming I can use in MFC. Often the MFC wrappers use
 CA> the same syntax as the API equivalent, and if not: I just call the
 CA> function I know.
Yes.
 CA> Most people starts with programming to the Windows API, because it is
 CA> important to know what is behind the fancy OOP libraries.
Yes. But that's because MFC is a very poor OOP lib for that case. It's as you
stated before a very thin wrapper, nothing more. Anyone expecting true object
behavior will fall on face. (Like I did. :)  Fortunately it's quite well
armored with asserts so you can relatively easily figure out what happened. I
expected that controls and such elements will handle themselves, but they do
nothing but giva another form of calling the same old API functions. If
they're not on screen you simply get an assert termination or in release
version probably a lockup.
Paul
... You're not as real as you think
--- OS/2 Warp
---------------