Difference between revisions of "Beginner C++ Game Programming Tutorial 4"
(→Notes!) |
(→Notes!) |
||
| Line 4: | Line 4: | ||
This video has a high dropout rate. First of all, at around 12:22 ~ 12:30 I delete two lines (lines 45 & 46 in Game.cpp), but I don't show it in the video. Make sure you delete them at around that time. If you're having trouble with the concepts of this video, or getting the code or the homework done, don't just give the fuck up! Visit us on the forum or the Discord and get some help! Or at least leave a comment on the YouTube video. | This video has a high dropout rate. First of all, at around 12:22 ~ 12:30 I delete two lines (lines 45 & 46 in Game.cpp), but I don't show it in the video. Make sure you delete them at around that time. If you're having trouble with the concepts of this video, or getting the code or the homework done, don't just give the fuck up! Visit us on the forum or the Discord and get some help! Or at least leave a comment on the YouTube video. | ||
| − | From a YouTube comment: | + | From a YouTube comment: <br/> |
<small>I also had a hard time understanding how setting the variables in game.h causes the reticle to have different behavior compared to setting them in the local scope. I think its because when the local scope is looped game.h allows the program to remember where the reticle was in the previous iteration, but leaving it in game.cpp forces it to be reset after each loop. Maybe that could be made clearer somehow, because it took me a while to get what was going on. | <small>I also had a hard time understanding how setting the variables in game.h causes the reticle to have different behavior compared to setting them in the local scope. I think its because when the local scope is looped game.h allows the program to remember where the reticle was in the previous iteration, but leaving it in game.cpp forces it to be reset after each loop. Maybe that could be made clearer somehow, because it took me a while to get what was going on. | ||
Revision as of 23:12, 31 December 2016
In this tutorial we explore the idea of animation in computer graphics and we make the reticle move freely around the screen. Along the way we learn how to add member variables to objects/classes, we learn about .h (header) and .cpp files, we learn about the short harsh lives of variables (scope), and I make a joke in very bad taste. All par for the course!
Contents
Notes!
This video has a high dropout rate. First of all, at around 12:22 ~ 12:30 I delete two lines (lines 45 & 46 in Game.cpp), but I don't show it in the video. Make sure you delete them at around that time. If you're having trouble with the concepts of this video, or getting the code or the homework done, don't just give the fuck up! Visit us on the forum or the Discord and get some help! Or at least leave a comment on the YouTube video.
From a YouTube comment:
I also had a hard time understanding how setting the variables in game.h causes the reticle to have different behavior compared to setting them in the local scope. I think its because when the local scope is looped game.h allows the program to remember where the reticle was in the previous iteration, but leaving it in game.cpp forces it to be reset after each loop. Maybe that could be made clearer somehow, because it took me a while to get what was going on.
After watching the video 3 times I fully understood it though.
When the x and y variables are declared in the ComposeFrame() function, they are getting created and destroyed every frame, and thus there is no continuity of the values between frames (they are being reset every time). When they are declared in Game.h, in the class declaration of Game, they become part of the game object and thus they remain alive across function calls and retain their values from one call of ComposeFrame() to the next.
Again, if this is too complicated you should ask for help on the forum or the Discord.
Concepts Taught
- Animation and double buffering
- Difference between .h and .cpp files
- Difference between a
classand an object - Adding member variables to a
class - Variable scope
Video Timestamp Index
- Intro 0:00
- Keyboard Ghosting 0:29
- Animation and double buffering 1:15
- Animation sequence in the Framework 4:54
- Variable scope (lifetime) 7:28
- Difference between object and
class9:15 - Difference between .h and .cpp source files 10:25
- Adding member variable to a
class11:15 - Variable scope name hiding 11:42
- Member access for members of same
class13:12 - Homework 13:54
Homework
This lesson has three homework problems. Feel free to attempt any or all of them.
- Separate the game logic code from the drawing code. The game logic code should go in the
Game::UpdateModel()member function, and the drawing code should remain inGame::ComposeFrame(). - Change the behavior of the reticle so that it moves at a velocity that is controlled with the arrow keys. This means that the arrow keys don't control direction of movement, but that they control the acceleration.
- Make it so that the acceleration of the reticle is more controllable. How this is accomplished is left up to you. Full marks for using only concepts introduced so far ;)
The solutions are given in this video.
Solution Errata
Read the below (click Expand) only after attempting the problem yourself.
In the solution (3:32), Chili declares (in Game) a bool variable controlIsPressed to signal that the shape should be changed. First of all, the key being pressed is the SHIFT key, so this is confusing.
Secondly, a better name for this variable would have been isBoxMode, since the drawing code doesn't really care what key was actually pressed, all it wants to know is what shape it should be drawing. This doesn't affect the behavior of the program in any way, but it makes it more logically coherent.
