Difference between revisions of "Beginner C++ Game Programming Tutorial 4"
(→Errata) |
(→Note) |
||
| Line 48: | Line 48: | ||
In Part 3 when we make the <code>gb</code> variable a member variable, it will maintain its value from frame to frame. So if we don't reset it every frame, then the first time we press CTRL and set it to 255, it will forever after be stuck at 255, which is probably not desired behavior. ;) | In Part 3 when we make the <code>gb</code> variable a member variable, it will maintain its value from frame to frame. So if we don't reset it every frame, then the first time we press CTRL and set it to 255, it will forever after be stuck at 255, which is probably not desired behavior. ;) | ||
| − | == | + | == Notes == |
| − | This is version 2 of this tutorial. Version 1 was released back in August 2016, but it caused a lot of people to lose their shit and give up on the awesomeness that is C++, so Chili remade it. It's now over twice as long, and jam packed full of juicy knowledge, with a liberal smattering of memes as well. | + | * If you get a crash when the reticle goes off the screen when Chili can make his reticle wrap from right to left, make sure your build configuration is set to <code>Release</code> and not <code>Debug</code>. |
| + | * This is version 2 of this tutorial. Version 1 was released back in August 2016, but it caused a lot of people to lose their shit and give up on the awesomeness that is C++, so Chili remade it. It's now over twice as long, and jam packed full of juicy knowledge, with a liberal smattering of memes as well. | ||
== See also == | == See also == | ||
* [[Beginner C++ Game Programming Tutorial 5|Next in series (Tutorial 5)]] | * [[Beginner C++ Game Programming Tutorial 5|Next in series (Tutorial 5)]] | ||
* [[Beginner C++ Game Programming Series]] | * [[Beginner C++ Game Programming Series]] | ||
Revision as of 13:06, 31 May 2018
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 about classes and objects, how to add member variables to objects/classes, about .h (header) and .cpp (source) files, and about the short harsh lives of local variables (scope).
Contents
Concepts Taught
- Animation and the game loop
- Variable scope
- The concept of objects
- Classes and their relation to objects
- Data members (member variables) and member functions
- Difference between .h and .cpp files
- Adding data members to a
class - Separating logic and drawing code
Video Index
Bonus Advice Video
The bonus video mentioned at the end of Part 3 with advice for beginners hasn't been made yet. Wait first eh! It will be made in due time, and when it is you will get a notification if you put good old Chili in your notification list for YouTube. I'll put the link here as well when the video gets made and uploaded. Until then, don't take any wooden nickels or whatever.
Homework Questions
This lesson's homework is to answer the following questions. When you think you have the answer, click "expand" to reveal the correct answer.
1. What symbols are a common indicator of the scope of a local variable?
A: The curly braces {}.
2. What are the two types of members that define a class?
A: Data members and member functions.
3. What is the relationship between classes and objects.
A: Classes are like a template or a blueprint that specifies the shape of an object. Objects are data structures in memory that are created, shaped, and which behave based on how they are specified in their class. We say that an object is an instance of a class.
4. How do we achieve the movement of the reticle.
A: We achieve movement of the reticle by making the variables x and y member variables of class Game. In doing so, we no longer lose the values of these variables from frame to frame (when they are local variables, they are destroyed after exiting the ComposeFrame() function, i.e. after each frame).
5. How are the members gfx and wnd in class Game different?
A: Game::gfx is an object which is embedded directly into objects of the Game class, whereas Game::wnd is a reference to a MainWindow object that exists outside of and is independent of the Game object.
Errata
In Part 1 at 6:00 there is a mistake in the diagram where Chili shows the concept of animation from one frame to the next. The "frame 2": "draw 2nd object" (blue triangle) should have the blue triangle drawn to the right as it is shown in "draw 3rd object".
In Part 3 when we make the gb variable a member variable, it will maintain its value from frame to frame. So if we don't reset it every frame, then the first time we press CTRL and set it to 255, it will forever after be stuck at 255, which is probably not desired behavior. ;)
Notes
- If you get a crash when the reticle goes off the screen when Chili can make his reticle wrap from right to left, make sure your build configuration is set to
Releaseand notDebug. - This is version 2 of this tutorial. Version 1 was released back in August 2016, but it caused a lot of people to lose their shit and give up on the awesomeness that is C++, so Chili remade it. It's now over twice as long, and jam packed full of juicy knowledge, with a liberal smattering of memes as well.
