Go Down

### Topic: Simon Game programming (Read 4301 times)previous topic - next topic

#### Vincent19

##### Jan 22, 2013, 01:39 pmLast Edit: Jan 22, 2013, 01:43 pm by Vincent19 Reason: 1
This is the whole coding for the simon game. I am curious about how the code flow since each function do not return anything. And I am curious about this part:
Code: [Select]
`void input(){  for (int x=0; x <= turn;)  {    input1 = digitalRead(SWITCHROOT);    input2 = digitalRead(SWITCHROOT+1);    input3 = digitalRead(SWITCHROOT+2);    input4 = digitalRead(SWITCHROOT+3);    counter++;          if (counter > RESPONSETIME)    {      Serial.println("TIMEOUT!");      fail(randomArray[x]);      counter = 0;      x++;    }`
Does that means that we need to respond faster as the counter increases ?

Thanks

#### PaulS

#1
##### Jan 22, 2013, 02:20 pm
Quote
This is the whole coding for the simon game.

No, it isn't.

#### Vincent19

#2
##### Jan 22, 2013, 02:23 pm
The whole code in the text file as it exceed the word limits.

Thanks

#### robtillaart

#3
##### Jan 22, 2013, 09:28 pm
you can attach as zip file
Rob Tillaart

Nederlandse sectie - http://arduino.cc/forum/index.php/board,77.0.html -
(Please do not PM for private consultancy)

#### Vincent19

#4
##### Jan 23, 2013, 02:41 am
Cant be view now ?

#### johncc

#5
##### Jan 23, 2013, 03:01 am

This is the whole coding for the simon game. I am curious about how the code flow since each function do not return anything.

In certain terminologies, functions which don't return anything are called "procedures".
Your example code is well-written, IMO.

Quote

Code: [Select]
`void input(){  for (int x=0; x <= turn;)  {    input1 = digitalRead(SWITCHROOT);    input2 = digitalRead(SWITCHROOT+1);    input3 = digitalRead(SWITCHROOT+2);    input4 = digitalRead(SWITCHROOT+3);    counter++;          if (counter > RESPONSETIME)    {      Serial.println("TIMEOUT!");      fail(randomArray[x]);      counter = 0;      x++;    }`
Does that means that we need to respond faster as the counter increases ?

No, it means if too much time has elapsed, you lose.  Big clues are: "TIMEOUT!" and "fail"

HTH,
John

#### Vincent19

#6
##### Jan 23, 2013, 03:05 am
But is it true that every turn I have 3s of timeout time ? But it seems to me not on hardware ><

Well, procedures so means once it done execute the output code, then it will automatically go to input code ? Flow according to the code ?

Thanks

#### johncc

#7
##### Jan 23, 2013, 03:12 am

Does that means that we need to respond faster as the counter increases ?

Code: [Select]
`///////////////////////////////////////////////////////////////////////////// Slowly cranks up the pressurevoid increaseSpeed(){  if (turn == band)  {    beepdelay = 170;    pausedelay = 80;    return;  }  if (turn == band * 2)  {    beepdelay = 150;    pausedelay = 60;    return;  }  if (turn == band*3)  {    beepdelay = 120;    pausedelay = 40;  }}///////////////////////////////////////////////////////////////////////////void loop(){ for (int y = 0; y < WINSTATE; y++) {   output();   input();   increaseSpeed();  // <---------------------------------- THIS is the part that makes it go faster as the game proceeds }                                                               It calls the procedure "increaseSpeed" defined above win(); }`

in the "for" loop above, until the player either wins or loses, the output code is executed, then the input code is executed, then increasespeed, and then back to output, etc.

John

#### Vincent19

#8
##### Jan 23, 2013, 03:16 am
Ok, the speeed of the output goes faster. However, based on the full coding, does it means that the time I need to respond also getting faster ? Cause I seems to feel it when playing it ><

Ok, so either the player win or lose, it will follow the sequence : output > input > increase speed. And the final win(); is for what ?

Thanks

#### johncc

#9
##### Jan 23, 2013, 03:33 am

Ok, the speeed of the output goes faster. However, based on the full coding, does it means that the time I need to respond also getting faster ? Cause I seems to feel it when playing it ><

I don't think so, because RESPONSETIME is a defined constant and doesn't get changed.
Quote

Ok, so either the player win or lose, it will follow the sequence : output > input > increase speed. And the final win(); is for what ?

Up above is the definition of the win() "procedure".  Looks like it beeps a certain way and flashes all the lights.

The loop() procedure at the bottom of the code is called over and over by the Arduino framework code. Therefore, win or lose, the player gets to keep going (but I think the score is reset once you lose).  http://arduino.cc/en/Reference/Loop

The loop() procedure "high-level" code being at the bottom is typical of c and c++ coding style, with the definitions of the procedures/functions/subroutines above.

Note I am answering these questions from quick, cursory examination of the code because it is well organized, factored, and very good names for the variables.  (But I could have missed something )

Have you programmed in any other languages?  If so, what?

#### Vincent19

#10
##### Jan 23, 2013, 04:02 am
No..just arduino languages. So , win() will only be call once the for loop finish executing in void loop() ?

#### johncc

#11
##### Jan 23, 2013, 04:15 am

No..just arduino languages. So , win() will only be call once the for loop finish executing in void loop() ?

Yes, it will be called after y<WINSTATE becomes false.  WINSTATE is defined as 32 so it appears that the for-loop will loop 32 times.

#### Vincent19

#12
##### Jan 23, 2013, 04:38 am
I am very curious and dont understand for the part if(counter> RESPONSETIME)

How is that ? the counter will increase in every loop, so in every loop it is getting closer to exceed RESPONSETIME isnt ?

#### johncc

#13
##### Jan 23, 2013, 04:49 amLast Edit: Jan 23, 2013, 04:52 am by johncc Reason: 1

I am very curious and dont understand for the part if(counter> RESPONSETIME)

How is that ? the counter will increase in every loop, so in every loop it is getting closer to exceed RESPONSETIME isnt ?

Yes.  It looks like the player has something slightly over 3 seconds (RESPONSETIME=3000) to push the buttons in proper sequence, or else he fail().

#### Vincent19

#14
##### Jan 23, 2013, 04:51 am
slightly over 3s ? not less than 3s ?

Go Up