# Selection Structures - Car Scrolling Game

![main1.png](images/main1.png)
![main2.png](images/main2.png)
![main3.png](images/main3.png)

[Verano 2016 - Ive - Coralys]

Commonly, when solving a problem, we select among several choices depending on whether certain conditions are met. Computer programs are built to solve problems, so they should have a structure that allows them to make decisions and select alternatives. In C++ selections are structured using `if`, `else`, `else if` or `switch`. Relational expressions and logical operators are common when handling selection structures. In today's laboratory experience you will practice the use of certain selection structures to complete the design of a car and an obstacle collision game application. 

## Objectives:

1. Use relational expressions and select appropriate logical operators to make decisions.
2. Apply selection structures.


## Pre-Lab:

Before arriving at the laboratory you should have:

1. Reviewed the following concepts:

      a. Logical operators

      b. if, else, else if, switch

2. Studied the concepts and instructions for the laboratory session.

3. Taken the Pre-Lab quiz, available in Moodle.


---

---


## Car Scrolling Game

Collision games consist of maneuvering an object in order to dodge incoming objects to avoid possible collision. The collision can lower the player's score, or stop the game. Sometimes, colliding with certain objects may increase the player's score. In the game from today's laboratory experience, the object the player controls is a car, the objects that cause the game to stop are pines, holes, among others; and the objects that add points to the score are flags.

The controls for this game are simple: the up arrow moves the car up, and the down arrow moves the car down. During gameplay, the game simulates the movement of the car towards the right using a simple method: moving the background with its obstacles and flags towards the left while the car stays in the same place. The player can move the car up or down to dodge obstacles and to capture the flags. If the car collides with an obstacle, the game ends. The player can continue by pressing the `Retry` button. 


---

---

!INCLUDE "../../eip-diagnostic/car-scrolling/en/diag-car-scrolling-01.html"
<br>

!INCLUDE "../../eip-diagnostic/car-scrolling/en/diag-car-scrolling-02.html"
<br>

---

---


## Laboratory Session:

In this laboratory experience, you will practice the use of mathematical expressions and condition structures to implement the car's collision detection against obstacles and flags.

Your task is to complete the design of the game application.

### Exercise 1 - Familiarize yourself with the pre-defined functions

The first step in this laboratory experience is to familiarize yourself with the pre-defined functions (methods) in the code. You will invoke some of these functions in the code to detect the collisions. 

#### Instructions:

1. Load the project  `CarScrollingGame` into `QtCreator`. There are two ways to do this:

       * Using the virtual machine: Double click the file `CarScrollingGame.pro` located in the folder `/home/eip/labs/conditionals-carscrollinggame` of your virtual machine.
       * Downloading the project’s folder from `Bitbucket`: Use a terminal and write the command `git clone http:/bitbucket.org/eip-uprrp/conditionals-carscrollinggame` to download the folder `conditionals-carscrollinggame` from `Bitbucket`. Double click the file `CarScrollingGame.pro` located in the folder that you downloaded to your computer.

2. Configure the project. The project consists of various files. **You will only write code on the file** `work.cpp`**. You should not change anything on the other files.**

3. You are going to need a few methods defined in the following files to create your code.

       * `car.h` y `car.cpp`: contains the definition of the class `Car`, the methods of the class and their declarations.
       *  `flag.h` y `flag.cpp`: contains the definition of the class `Flag`, the methods of the class and their declarations.
       *  `obtstacle.h` y `obstacle.cpp`: contains the definition of the class `Obstacle`, the methods of the class and their declarations.
       * `play.h` y `play.cpp`: contains the definition of the class `Play`, the methods of the class and their declarations.

       Familiarize yourself with the methods in these files. Emphasize the following methods:

       * `Car::getYCar()`: Returns the $$Y$$ coordinate of the car's position on the track.
       * `Flag::getXFlag()`: Returns the $$X$$ coordinate of the flag's position on the track.
       * `Flag::getYFlag()`: Returns the $$Y$$ coordinate of the flag's position on the track.
       * `Flag::hide()`: Hides the flag.
       * `Obstacle::getXObstacle()`: Returns the $$X$$ coordinate of the obstacle's position on the track.
       * `Obstacle::getYObstacle()`: Returns the $$Y$$ coordinate of the obstacle's position on the track.
       * `Play::setScore(n)`: Receives an integer number and adds it to the game's total score.
    
       There isn't a `getXCar()` method because the car does not move on the $$X$$ axis.

### Exercise 2 - Complete the function to change the game's track.

In this exercise you will use the C++ condition structure called **switch** to change the attributes of the track. You will complete the `setTrack` method that can be found in the `work.cpp` file. This method changes the environment of the track depending on the value of `track_type` that is given as a parameter.

The method `setTrack` receives a value of type `Track` that can be:

   * `play::DAY` - for a day track
   * `play::NIGHT` - for a night track
   * `play::BEACH` - for a beach track
   * `play::CANDYLAND` - for a candy track

The track's attributes that can be changed are:

   * the image on the track using the function `setTrackPixmap()`
   * the image of the obstacles using the function `setObstaclesPixmap()`

The `setTrackPixmap()` function is already defined and receives a variable of type `Track` that can be one of the following: **play::DAY**, **play::NIGHT**, **play::BEACH**, **play::CANDYLAND**.

The `setObstaclesPixmap()` function is already defined and receives a variable of type `string` that can be one of the following: **"hole"**, **"cone"**, **"it"**, **"zombie"**, **"spongebob"**, **"patric"**, **"monster"**.

#### Instructions:

To complete the `setTrack()` function: 

1. Change the image on the track according to the `Track` value received.

2. Change the image of the obstacles using the `switch` selection structure such that the obstacles change according to the value received by `setTrack()`. If the type of the track that is received is:

    * `play::DAY` - the obstacles are of type "hole" or "cone"  
    * `play::NIGHT` - the obstacles are of type "it" or "zombie"
    * `play::BEACH` - the obstacles are of type "spongebob" or "patric"
    * `play::CANDYLAND` - the obstacles are of type "monster"

    With the options that have two possible obstacles use `rand() % 2` to randomly select between an obstacle or the other.

### Exercise 3: Complete the function for collision with obstacles

In this exercise you will complete the `obstacleCollision` method that can be found in the `work.cpp` file. The function receives an object of the `Obstacle` class and another object of the `Car` class, and should detect if there is a collision or not between the car and the obstacle. The function returns true if there is a collision between the car and an obstacle, and false if there is no collision.

To detect the collision, the function should ask for the coordinates of the obstacle and the car's $$Y$$ coordinate. Remember that the car does not move on the $$X$$ axis, since that coordinate is fixed and stored in a constant variable called `CARX`. The collision occurs if the obstacle has the same $$X$$ coordinate, and is a certain distance above and below the car's $$Y$$ coordinate as shown in Figure 1. The range of the distance of the car's center upwards and downwards is stored in the variable called `OBSTACLERANGE`.

If a collision is detected, the function returns `true`, and if not the function should return `false`.

---

![ColisionC.png](images/ColisionC.png)

**Figure 1.** The image shows the coordinates $$(CARX,Y)$$ that the obstacle should have for a collision to occur.

---


### Exercise 4: Complete the function for collision with flags

In this exercise you will complete the `flagCollision` method that can be found in the `work.cpp` file. The function receives an object of the `Obstacle` class and another object of the `Car` class, and should detect if there is a collision or not between the car and the flag. This function is very similiar to the function in Exercise 3, except that the function does not return a value. The actions that occur when a collision is detected are done inside the function.

In this case if a collision is detected, the game's score should increase by 30 points using the `setScore` function and the flags should be hidden using the `flag.hide()` function to create the illusion that the flag was picked up during the collision.

---

---

### Deliverables

Use "Deliverable" in Moodle to upload the `work.cpp` file that contains the function calls and changes you made to the program. Remember to use good programming techniques by including the name of the programmers involved and documenting your program.

---

---

### References
[1] Dave Feinberg, http://nifty.stanford.edu/2011/feinberg-generic-scrolling-game/

