Is this Multi-Threading?

I want it to constantly run something UNTIL it receives a keypress like this

Code:

---

for ( ;; )
{ 
    Beep(x,10);
    _getch();
}

---

except that WAITS for the keypress before continuing with the loop. I need it to loop until it gets a keypress, effectively constantly beeping until a keypress. Basically, the keypresses will change the value of x, allowing the user to change the pitch.

Can anyone please help me?

No, that's not Multi-Threading, it acts i little like it
Could you tell use what compiler you're using?
What headers?
What kind of program?

That sounds like it would work, but how do I get it to store that? How could I get it to store the keypress (when it comes?)

I need to have it check if it was

W
A S D

I was going to make it be the arrow keys, but you need to have two ASCII values and I don't know how to do that.

Thanks!

Yeah, I use kbhit() like vVv shows every day, 'cause we run test loops that run 'till a key is pressed. I was thrilled when I discovered kbhit()!!!

I think that after you exit the loop getch() will read your keypress that's left in the buffer... not sure... you'll have to try it, or wait for an answer from sombody who knows what he's talking about!

Code:

---

char which;
do
{
  while (!kbhit())
  {
      // Do something
  }
  which = tolower(getch());
}
while (which != 'w' || which != 's' || which != 'a' || which != 'd');

---

Eibro, thats great, but one question: would it be simple to change that to the arrow keys? I know that they require two ASCII values, or at least seem to.

Well multi threadin is always better and more advantageous.. using kbhit() for simple apps will make it work well... But the fact remains that only one instruction is being executed at any given time.....

I wrote many games that are animated using kbhit() but the problem was when a key was pressed the statements inside the (!kbhit()){ } is run.. and in case you use a delay or something here the entire animation slows down.. but a small price to pay for that advantage........

Quote:

---

Eibro, thats great, but one question: would it be simple to change that to the arrow keys? I know that they require two ASCII values, or at least seem to.

---

Strangely enough... I simply set mine up to look for a 72 for UP and it recognized it. Problem is you need to find a way for it to not think that's a capital H.

Do this:

Code:

---

if (key_pressed = 0)
{
  zero_pressed = 1;
}
switch (key_pressed)
{
  case 72:
    if (zero_pressed == 1)
    {
      key_pressed = 1000;  /* UP */
      zero_pressed = 0;
    }
    else
    {
      key_pressed = 72;
    }
    break;
  case 75:
    if (zero_pressed == 1)
    {
      key_pressed = 1001; /* LEFT */
      zero_pressed = 0;
    }
    else
    {
      key_pressed = 75;
    }
    break;
  case 77:
    if (zero_pressed == 1)
    {
      key_pressed = 1002; /* RIGHT */
      zero_pressed = 0;
    }
    else
    {
      key_pressed = 77;
    }
    break;
  case 80:
    if (zero_pressed == 1)
    {
      key_pressed = 1003; /* DOWN */
      zero_pressed = 0;
    }
    else
    {
      key_pressed = 80;
    }
    break;
}

---

I've typed this from memory, so I don't quite remember if it works or not. But if it did, I think it was virtually error free. The zero_pressed takes care of the problem of it thinking the arrowkeys are letters (up is H and something is M, but I don't really remember).