You do not have to memorize everything. Just learn the main ideas, and then do something to try it out. The exact spelling you can check from the Programmer''s Reference while writing the code.
I also recommend copy-pasteing bits of code directly from the tutorials and samples.

I know what you mean, I used to have the same problem. Learning the core commands and usage of DX is not very natural (at least it wasn't to me). When I first started, I tried to follow the books and make a simple game. That didn't work for me. I could make a simple 2D game by modifying someone's code, but I didn't REALLY know what was going on in there.

a) Don't try to make a game right away. Try making a screen that displays a bitmap. I don't mean modify the DDraw samples, I mean do it from scratch and learn exactly what is going on. It's hard to do when you have a vision of a game or something you want to make now, but it was totally necessary for me. From there, dig into the docs and figure out the best way to add a cursor to your bitmap. From there, add the ability to click on areas and jump to different bitmaps. Before you know it, you will have a menu system.

b) Start a library of generic helper functions and classes. For me it was too complicated to remember how to setup DX, or process keyboard or mouse input or even load a bitmap. So I began making classes and functions that handled these things in a generic way. Now I don't have to remember the correct DX calls and what order to call them in, I just need to know my function and exactly how IT works.

So basically, my tip to all the newbies is use the power of C++. If you don't know about inheritance or polymorphism yet, go find out about them and try to use them wherever you can, because it will make your life a whole lot easier!
It can also make your code much more readable.

Also, always remember that ANYTHING that is too complicated can be broken up into multiple simple problems.

Good Luck!

BigCarlito



Edited by - BigCarlito on 2/9/00 4:11:21 PM

It''s not as important to memorize something as it to know that you can do that thing. If you know it''s doable you can look it up when you need to do just that thing.

I''ve been programming for a very long time and I still need to check the manual for simple things as printf or operator priorities once in a while. But since I have read it before and understood then, I only need to take a quick glance at the text and it comes right back to me.

Well, the posts above mentioned the main things I agree with ''em.
Try to make small programs that display some bitmaps, sprites, etc. Then try to make a small game with this stuff. Think about the design of your small game and the rest will come automatically.

I had the same problem. The key is to any API is understanding how to initialize it. In DirectX, breakup the initialization code, the enumeration code(device search), and the communications code into small pieces this helped me get a handle on DirectX. For instance, with DirectDraw you must call DirectDrawCreate(Ex)(), SetCooperativeLevel(), SetDisplayMode(), and CreateSurface() before you can begin drawing anything. Also any one of these methods can fail if you pass an invalid pointer or parameter.

Here are some tips:
Always make sure you understand what the various parameters of a function are for. This is by far more important than memorizing the functions. You can always look them up.

Whenever pointers are being passed, make sure they are valid (not equal to NULL).

Always check the return values for the DX functions in cross - dependent code before continuing. This affords you an opportunity to exit gracefully if a call fails, popup a messagebox explaining what failed, or to output a debug string. Plus such code can be easily removed during performance tuning.

Don''t ever assume a DX function returned successfully. Youd be surprised how often problems arise from this ''stupid'' mistake. Always check return values!!

Enumerate whenever writing mission critical code. I admit to not always enumerating during debugging/pre - alpha, but you must enumerate in commercial apps. If you don''t you will end up with software that only works on your personal development machine.

PS. If you want some code or some help post a reply to this message with your email address and I will get back to you. I have been contemplating writing an implementation-centric game/graphics programming book with special coverage of D3D, but until I do, you maybe should consider buying Inside DirectX. The material is dated (DX5), and doesn''t cover D3D, but I strongly advocate their approach to DX programming and the book is fairly thorough. The book also covers some key concepts of COM and most of the methods used in the book are still supported by DX7.

I had the same problem. The key is to any API is understanding how to initialize it. In DirectX, breakup the initialization code, the enumeration code(device search), and the communications code into small pieces this helped me get a handle on DirectX. For instance, with DirectDraw you must call DirectDrawCreate(Ex)(), SetCooperativeLevel(), SetDisplayMode(), and CreateSurface() before you can begin drawing anything. Also any one of these methods can fail if you pass an invalid pointer or parameter.

Here are some tips:
Always make sure you understand what the various parameters of a function are for. This is by far more important than memorizing the functions. You can always look them up.

Whenever pointers are being passed, make sure they are valid (not equal to NULL).

Always check the return values for the DX functions in cross - dependent code before continuing. This affords you an opportunity to exit gracefully if a call fails, popup a messagebox explaining what failed, or to output a debug string. Plus such code can be easily removed during performance tuning.

Don''t ever assume a DX function returned successfully. Youd be surprised how often problems arise from this ''stupid'' mistake. Always check return values!!

Enumerate whenever writing mission critical code. I admit to not always enumerating during debugging/pre - alpha, but you must enumerate in commercial apps. If you don''t you will end up with software that only works on your personal development machine.

PS. If you want some code or some help post a reply to this message with your email address and I will get back to you. I have been contemplating writing an implementation-centric game/graphics programming book with special coverage of D3D, but until I do, you maybe should consider buying Inside DirectX. The material is dated (DX5), and doesn''t cover D3D, but I strongly advocate their approach to DX programming and the book is fairly thorough. The book also covers some key concepts of COM and most of the methods used in the book are still supported by DX7.

--Sickened with the World,
Cauldron the Melancholy