Game Development Reference
In-Depth Information
Figure 6-11
.
Modify the body of the .handle() method for each of four Button controls to complete the infrastructure
As you can see, you are leaving the gameButton.setOnAction() event-handling
structure empty for now; in the next chapter, you will create the primary game play sur-
face and a pulse event-processing engine (structure) that will run this game by calling
the various functional engines that you will be writing over the course of the topic.
You are leaving the bottom part of the high scores screen blank for now as well so
that you can overlay the two ImageView layers with a TableView Node object in your
Scene Graph root StackPane. You will complete this composite for the High Scores
button UI element later on after you finish developing your Java 8 game.
Now, it is time for the final testing of the top-level UI part of your game application
to make sure that all the UI button elements (objects) function properly and do what
you have designed (coded) them to do. After that, you will be running the NetBeans
8.0 Profiler again to ensure that the Scene Graph hierarchy that you have just created is
indeed leaving 99 percent of the available CPU processing power for the game engines
that you will be creating from here on.
Testing the Final InvinciBagel UI Design
