Chapter 4 Programming Challenge 22 Java Slot Machine

Chapter 4 Programming Challenge 22 Java Slot Machine Free Play
Chapter 4 Programming Challenge 22 Java Slot Machines
Chapter 4 Programming Challenge 22 Java Slot Machine Download
Chapter 4 Programming Challenge 22 Java Slot Machine Machines

Page 84: Chapter 4 Figure 4-22 Chapter 4: Troubleshooting Table 4-4 Tilt Codes (continued). Display Definition Possible Solution(s) Hopper Tamper The OS detected that the coin Check Hopper coin out switch. Pulse was too short or the coin pulse occurred during no payout.

A couple of years ago, when I was learning Java programming, I thought of testing myself and my programming skills by writing a game in Java. Now, I'm not going to call it 'game programming', since game programming is way more than what I did. In fact, what I did was just a test for me. So I decided to write a game I was playing on my old Nokia E50 phone, a Slot Game.

This slot game I was playing on my phone was really simple. It had only 3 slots with different items in each. You had to push the Spin button in order to spin the slots, and you would win a small amount of coins if two or three slots were alike. Of course, 3 slots were better than 2. It is not really hard to make a game like this, but for a beginner it is good to start with. As I remember, this was probably the first program that I could tell others: “Look at what I just did!”

So I started working on it (I remember using NetBeans at that time), firstly as console-only, and then using GUI. The first thing I did, was deciding what kind of images (actually their names, not the images themselves) I would use. I wrote this line of code:

I also decided what would be the amount of “money” that the user would win if he matched two or three symbols:

After that, I went on writing the code that was suposed to randomly choose one of the elements in the symbols array. This could be done by using the Math.random() method, or by calling the nextInt() method at a Random instance, or by the wrong way I used to do at the beginning:

Of course, I soon switched to calling Math.random(), and in order to get a number that I could use as an index for my array, I wrote this block of code:

So the variable choice was the random index that I could use to get a random item from the array (keep in mind that Math.random() returns a double between 0.0 and 1.0)

So after choosing 3 random items, I just printed them out at the console, saying whether there were none, two or three matches, and calculating the amount of money won, if there was any, with the given coefficient. It was a good start; I only had to think of the UI, and I suck at UI design. But for this one, all that I needed was a really simple design which I managed to code as I was planning.

For the items to show at slots, I just googled them and found 12 of them in a single sprite. I downloaded the sprite and started my old photo editing software which sometimes can really be magical; Microsoft Paint! I started cropping images from the sprite, paying attention to their dimensions that should be the same, 122px by 114px. Why these magical values? Just because!

What was left to do, was the UI. I could use the really-helpful drag-and-drop UI builder that ships with NetBeans, but I wanted to do it myself. I had a really hard time figuring out which kind of layout to use, since the only one I really knew was GridLayout. Anyway beside that, I managed to use FlowLayout and BorderLayout. There is a difference between them, but I’m not really capable of pointing that out, so you can check the online JavaDoc for them.

I managed to build the game, and started to play it. I figured out that the coefficients for multiplying the bet were too damn high, but I didn’t care as long as I knew that the game worked.

My bad practices

As you can see, the source code of this simple game is in only one file. This is something that I don’t like to do anymore. A better way to do it is by making the code as modular as it can be. By building small modular elements, dividing the UI from the logic of the application, you help yourself during the testing and debugging phase. So the first thing that I would like to change, is dividing the whole class Slots extends JFrame from the class that calls it.

This is done by firstly creating a file called Slots.java that will contain only the code for the UI. Then, creating an ActionListener that will listen to different button clicks (there are 5 different buttons). Finally, creating a class called App.java that will only create a Slots instance and make it run.

Basically, the App.java would look like this:

As I remember, SwingUtilities.invokeLater() is used to divide the UI thread from other threads, so if any UI changes are needed, they won’t stall the application.

The Listener class, which might be called something like SlotButtonListener, might be something like this:

And finally, in the Slots class there would be only the code for defining the UI of the game. All the buttons would have SlotButtonListener as action listener.

Anyone who wants to change the code following these advices is free to do it. You can fork it anytime you want.

Do you have any Java programming advice for me? Feel free to comment below

textbooks for a first course in computer science
for the next generation
of scientists and engineers

Online content.

This booksite contains tens of thousands of files,fully coordinated with our textbook and also useful as a standalone resource.It consists of the following elements:

Execepts.A condensed version of the text narrative, for reference while online.
Lectures.Curated studio-produced online videos, suitable for remote instruction.
Java code.Hundreds of easily downloadable Java programsand our I/O libraries for processing text, graphics, and sound.
Data.Real-world data sets for testing code (ours and yours).
Exercises.Selected exercises from the book and “web exercises” developed since its publication,along with solutions to selected exercises.
Programming assignments.Creative programming assignments that we have used at Princeton.

You can explore these resources via the sidebar at left.

Introduction to Programming in Java.

Our textbook Introduction to Programming in Java[ Amazon· Pearson· InformIT]is an interdisciplinary approach to the traditional CS1 curriculum with Java.We teach the classic elements of programming,using an “objects-in-the-middle” approach that emphasizesdata abstraction.We motivate each concept by examining its impact on specific applications,taken from fields ranging from materials science to genomics to astrophysicsto internet commerce.The book is organized around four stages of learning to program:

Chapter 1: Elements of Programmingintroduces variables; assignment statements; built-in types of data;conditionals and loops; arrays; and input/output, including graphics and sound.
Chapter 2: Functionshighlights the idea of dividing a programinto components that can be independently debugged, maintained, and reused.
Chapter 3: Object-Oriented Programmingemphasizes the concept of a data type and its implementation, using Java's class mechanism.
Chapter 4: Algorithms and Data Structuresdiscusses classical algorithms for sorting and searching, and fundamental data structures, including stacks, queues, and symbol tables.

Computer Science.

Our textbook Computer Science[ Amazon· Pearson· InformIT]contains Introduction to Programming in Java as its first four chapters.The second half of the book explores core ideas of Turing,von Neumann, Shannon, and others that ignited the digital age.