To go on...Or not to go on...that is the ?
I am about to start learning tutorial six but first i have a question. I understand all that i have learned so far in tutorials 1-6 and i get how it all works, but if some one asked me to sit down and write a program that made a rotating three-D box (i can do this so far) that had a texture on it, I couldnt do it. I am having trouble "memorizing" texture mapping. I understand how it works, I just do not think I could write the code for it. Ive been stuck on this for about two weeks and I was wondering weather I had to have this memorized before I go on, or if it would even be reccomended.
Thanks for the help
Homepage
Luck is a Horse to ride like any other...Luckily im not a gambler, I dont know how to ride.
For any total noob out there Here is a like to my tutorials, thry them out
BoC HomepageLuck is a Horse to ride like any other...Luckily im not a gambler, I dont know how to ride.
May 15, 2003 07:14 PM
Don''t worry to much about that for now... you should know how it works but excact syntax is what refercence books are for... you should probably know the sequence of calls that need to be made to make a 3d cube with a texture.. my $0.02
Sit down and write a program that shows a textured box.
When you get stuck, check a reference, or NeHe. It''s much
easier to learn if you actually DO it, instead of just reading
about it.
--
MFC is sorta like the swedish police... It''''s full of crap, and nothing can communicate with anything else.
When you get stuck, check a reference, or NeHe. It''s much
easier to learn if you actually DO it, instead of just reading
about it.
--
MFC is sorta like the swedish police... It''''s full of crap, and nothing can communicate with anything else.
May 15, 2003 07:16 PM
You should know what each function does of course and know its name. What I would encourage you to do is write code that wraps up all the functions you''ve learned and make that code really easy to use. Trust me, even if you have to reference yourself to the code in the tutorials it will help you learn the code because you are using it in another context, in another way and thus you get a deeper understanding of what everything does. Those wrappers might be crap later on, but as you progress you should update them for what you need them to do, always keeping the functionality that you used to need before.
Good Luck.
Good Luck.
Remember, OpenGL is a tool. All you really have to remember is what it does.
Wrappers are also good ideas - it means you can easily switch between API''s when necessary.
Wrappers are also good ideas - it means you can easily switch between API''s when necessary.
Experienced programmers never memorize every single syntax. They have pieces of code saved so they can refer to them all the time. Simple as that ..... :}
______________________________
My Website: <link src="http://www.antondev.tk">
or directly at http://home.attbi.com/~antonweb/
"I''ve read about...doom being used to manage unix programs(you "kill" the processes)" dede
______________________________
My Website: <link src="http://www.antondev.tk">
or directly at http://home.attbi.com/~antonweb/
"I''ve read about...doom being used to manage unix programs(you "kill" the processes)" dede
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
Recommended Tutorials
Advertisement