COM & DirectX
COM helps - but it''s nor neccessary. I never use it. Basically and understanding helps because then you know how the objects interact and stuff.
==============================
"Need more eeenput..."
- #5, "Short Circuit"
Blade Edge Software
==============================
==============================
"Need more eeenput..."
- #5, "Short Circuit"
Blade Edge Software
==============================
Its not necessary to have a firm understanding of COM to lay down a first attempt at Direct X. Its only important to understand it when you upgrade exisiting code to a more recent version of Direct X. Look at example code and when it says QueryInterface, just take it on faith that you need to do that, because you do. Once you have the pointers its all downhill from there.
Hi
I read the book Inside COM+ Base Services form Microsoft Programming Series.
If you understand COM it helps a lot to understand
the strange things you have to do to prepare Direct3D
to work. Because then you see its really great and easy.
Especially when you write your own DirectX classes it helps
alot to understand COM.
But its not easy to learn it.
Bye
Lubos
I read the book Inside COM+ Base Services form Microsoft Programming Series.
If you understand COM it helps a lot to understand
the strange things you have to do to prepare Direct3D
to work. Because then you see its really great and easy.
Especially when you write your own DirectX classes it helps
alot to understand COM.
But its not easy to learn it.
Bye
Lubos
If you use DX8, you don''t really have to. And if you use DX7 for directdraw and the rest of DX8 you don''t really have to either. Because you''re not usually going to call QueryInterface if you use DX7 DirectDraw or DX8. And CoCreateInstance is not used either.
''Smile, things could get worse.''
So I smiled, and they did.
''Smile, things could get worse.''
So I smiled, and they did.
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement