User Tools

Site Tools


lab_7

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

lab_7 [2017/06/08 16:34]
hutch [Requirements]
lab_7 [2018/06/08 09:33] (current)
jgoeders [wamControl: What Does the Controller Do?]
Line 203: Line 203:
   - sends the coordinates of the touch to ''​wamDisplay''​ by calling the ''​wamDisplay_whackMole()'',​ passing the origin of the touch as the argument to the function.   - sends the coordinates of the touch to ''​wamDisplay''​ by calling the ''​wamDisplay_whackMole()'',​ passing the origin of the touch as the argument to the function.
  
-In addition, while waiting for the user to touch or while waiting for the touch ADC to settle, it activates ​moles whenever the number of active moles falls below the minimum allowed. That's about it.+In addition, while waiting for the user to touch or while waiting for the touch ADC to settle, it calls ''​wamDisplay_updateAllMoleTickCounts()''​ to update the mole tick counts, as well as activating ​moles whenever the number of active moles falls below the minimum allowed. That's about it.
  
 As you may have noted, the controller has no notion of how many moles are active, how many moles may be visible, or where the moles are located on the screen. It's primary job is to pass the coordinates of touches to ''​wamDisplay''​ routines to be processed. This makes it much easier to develop the display code so it can be very flexible. As the controller knows nothing about the positions of the moles, for example, the controller does not have to be changed when the mole count is changed from 9 to 6, for example. In either case the controller simply sends touch coordinates to the display software. The display software attempts to "​whack"​ the mole with the given coordinates. If the coordinates are over a mole that is awake, the display software erases the mole and increments the hit count in the score screen. Otherwise, the display software increments the miss value in the score screen. As you may have noted, the controller has no notion of how many moles are active, how many moles may be visible, or where the moles are located on the screen. It's primary job is to pass the coordinates of touches to ''​wamDisplay''​ routines to be processed. This makes it much easier to develop the display code so it can be very flexible. As the controller knows nothing about the positions of the moles, for example, the controller does not have to be changed when the mole count is changed from 9 to 6, for example. In either case the controller simply sends touch coordinates to the display software. The display software attempts to "​whack"​ the mole with the given coordinates. If the coordinates are over a mole that is awake, the display software erases the mole and increments the hit count in the score screen. Otherwise, the display software increments the miss value in the score screen.
Line 241: Line 241:
   * Milestone 2:   * Milestone 2:
     * Finish the game so that it meets all of the requirements.     * Finish the game so that it meets all of the requirements.
 +
 +==== Grading ====
 +
 +  * Milestone 1 Passoff: 35%
 +  * Milestone 2 Passoff: 35%
 +  * Lab 7 Code Submission: 30%.
 +
 +==== Submitting Source Code ====
 +Follow [[http://​ecen330wiki.groups.et.byu.net/​wiki/​doku.php?​id=submitting_source_code|this procedure]] to submit your source code to learning-suite.
 +
 +
  
 ---- ----
lab_7.1496961274.txt.gz ยท Last modified: 2017/06/08 16:34 by hutch