I''m soooo happy! I can FINALLY start bustin'' out some games!!!!
GO LEAFS GO!
One small step for the game industry, one giant leap for me!
Author
I just felt like announcing that I have completely completed my Win32 studies. This is no big deal for any of, but it is for me. 4 months ago, I picked up my first C++, I have no learned C++ to a high degree and finished off learning Win32. Now, I''d like to announce, I''m moving on to DirectX! I''m soooo happy! I can FINALLY start bustin'' out some games!!!!
GO LEAFS GO!
I''m soooo happy! I can FINALLY start bustin'' out some games!!!!
GO LEAFS GO!
Woo hoo, make some good ones Fredric!
"... you act as if stupidity were a virtue."
-- Flight of the Phoenix
"... you act as if stupidity were a virtue."
-- Flight of the Phoenix
Exactly...how far would one need to go into Win32 to be considered to have finished it off? I''m rather impatient to get to DirectX..but I''ve just recently started Win32 (and, of course, have nothing to learn from but MSDN Lib.).
BTW, I''m happy for you.
P h a n t a s m
"Through dreams I control mankind."
--Legend
BTW, I''m happy for you.
P h a n t a s m
"Through dreams I control mankind."
--Legend
Author
When I said I considered myself done with Win32 before going to DirectX, I basically used Andre LaMothe''s books as a guide. For example, if he said you would have to learn integers before moving on to functions, I''d do exactly that and no more. In this case, he considers the following to be in your head before going into DurectX:
1. Get to know the naming convention
2. Learn the different functions of a Windows skeleton.
3. Become comfortable with using the windows procedure.
4. Menus
5. Basic Input from the keyboard and mouse
6. Painting (hdc, WM_PAINT, GetDC/ReleaseDC, BeginPaint/EndPaint, pens, brushes)
7. Printing text
8. Lines, Points, Squares and Circles
9. Timers
10. Basics Sound
11. Dialog Boxes (dialog boxes, buttons, controls)
That''s about it! If you''re comfortable with making a windows application using all of the above to make a pretty cool program without using the book as a reference, then I think that''s the time you''ll be able to go on to DirectX. At least, that''s how I did it!
GO LEAFS GO!
1. Get to know the naming convention
2. Learn the different functions of a Windows skeleton.
3. Become comfortable with using the windows procedure.
4. Menus
5. Basic Input from the keyboard and mouse
6. Painting (hdc, WM_PAINT, GetDC/ReleaseDC, BeginPaint/EndPaint, pens, brushes)
7. Printing text
8. Lines, Points, Squares and Circles
9. Timers
10. Basics Sound
11. Dialog Boxes (dialog boxes, buttons, controls)
That''s about it! If you''re comfortable with making a windows application using all of the above to make a pretty cool program without using the book as a reference, then I think that''s the time you''ll be able to go on to DirectX. At least, that''s how I did it!
GO LEAFS GO!
Hehe, I don''t even remember any GDI painting, dialog boxes, etc, so if I need to use it I just look it up
Martin
Martin
Good luck!
"Remember, I'm the monkey, and you're the cheese grater. So no messing around."
-Grand Theft Auto, London
"It's not whether I win or lose, as long as I piss you off"
-Morrigan, Super Puzzle Fighter II Turbo
"Remember, I'm the monkey, and you're the cheese grater. So no messing around."
-Grand Theft Auto, London
"It's not whether I win or lose, as long as I piss you off"
-Morrigan, Super Puzzle Fighter II Turbo
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
