[JAVA][Beginning Java 8 Games Development]

Chapter 12 ■ Setting Boundaries for Your Action Figure in 2D: Using the Node Class LocalToParent Attribute
As you can see in Figure 12-6, the code is error-free, and you now have an .update() method that accesses the
Boolean variables from your InvinciBagel.java class without having to use any import static statements to do so.
You might be thinking, well, since this is a great way to get rid of import static statements in my Bagel.java class,
why don’t I use this same approach to also get rid of the static Bagel iBagel declaration in my InvinciBagel.java class,
as well as the import static statement that is used in the GamePlayLoop.java class to access the static iBagel Bagel
object? Wow, that is a fantastic idea, folks, I just wish that I had thought of it! In fact, let’s do that right now!
Removing a Static iBagel Reference: Revise the Handle( ) Method
As you can see in Figure 12-7, we still have quite a few InvinciBagel variables declared using the static keywords that
are not, in fact, constants. Before this chapter is over we will have eliminated these, so that only our WIDTH and
HEIGHT constants use the static modifier keyword. Since we are going to pass the InvinciBagel object reference
to the GamePlayLoop class using the Java this keyword inside of the GamePlayLoop() constructor method, which
means that we can remove the static keyword from the Bagel iBagel object declaration statement at the top of the
InvinciBagel class. This can be accomplished using the following variable declaration, which is shown (highlighted)
in Figure 12-7:
Bagel iBagel;
Figure 12-7. Remove the Java static modifier keyword from in front of your Bagel iBagel object declaration statement
The next thing that we’ll need to do to makes sure that our InvinciBagel and GamePlayLoop classes (objects) can
talk to each other is to make the GamePlayLoop() constructor method compatible with (accept in the InvinciBagel
this context reference object inside of its parameter list) the InvinciBagel class’s this object reference that we need to
send over to the GamePlayLoop class inside of the constructor method call. Since we are currently depending on the
Java compiler to create the GamePlayLoop() constructor method for us, we will need to create one for ourselves! As
you learned in Chapter 3, if you do not explicitly create a constructor method for a class, one will be created for you.
258
www.it-ebooks.info