Switch-Case inputs

Re: Switch-Case inputs

daniel_c_w — Tue, 16 Dec 2008 14:34:07 +0100

Is there a good Docu / API reference for WPAD?
I only found one for wiiuse.

Re: Switch-Case inputs

SpaceJump — Tue, 16 Dec 2008 09:00:59 +0100

Quote
ekeeke
Personnaly, I use a simple sleep() to delay after WPAD_Init before reading wiimote input

but maybe something like that might help you:
 u32 exp;
 while (WPAD_Probe(0, &exp) != WPAD_ERR_NONE);

Just tried this and it works! Thanks a lot.

Re: Switch-Case inputs

HyperHacker — Tue, 16 Dec 2008 08:02:52 +0100

Quote
Arikado
Quote
Tantric
That won't work at all. If you want to "slow down" you can try sleep() or usleep(). But this still wouldn't help you with what you're trying to do.
Funny, I've gotten it work in some of my past games. Usually 150 ends up being some insane number though, but it definitely works.

sleep() or usleep() is a better method though unless you need a very small delay (e.g. when interfacing with hardware that wants precise timing), as it lets the CPU idle, whereas your method pegs it at 100% usage. Less CPU usage means less heat, and is even more important on handhelds where it means longer battery life, and on multithreaded systems where it means the whole system isn't slowed down to a ridiculous extent.

Re: Switch-Case inputs

SpaceJump — Tue, 16 Dec 2008 07:34:48 +0100

Quote
bushing
Quote
SpaceJump
This didn't help:
for(int pause = 0; pause < 150; pause++){
}
What exactly does WPAD_GetStatus() return? When I try to printf it, I get errors.
"errors"?

Sorry, I meant Code Dumps.

Re: Switch-Case inputs

bushing — Tue, 16 Dec 2008 07:32:22 +0100

Quote
SpaceJump
This didn't help:
for(int pause = 0; pause < 150; pause++){
}
What exactly does WPAD_GetStatus() return? When I try to printf it, I get errors.

"errors"?

Re: Switch-Case inputs

SpaceJump — Tue, 16 Dec 2008 07:12:22 +0100

This didn't help:

for(int pause = 0; pause < 150; pause++){
}

What exactly does WPAD_GetStatus() return? When I try to printf it, I get errors.

Re: Switch-Case inputs

ekeeke — Mon, 15 Dec 2008 20:27:15 +0100

Personnaly, I use a simple sleep() to delay after WPAD_Init before reading wiimote input

but maybe something like that might help you:


 u32 exp;
 while (WPAD_Probe(0, &exp) != WPAD_ERR_NONE);

Re: Switch-Case inputs

daniel_c_w — Mon, 15 Dec 2008 18:01:13 +0100

Quote
Arikado
Quote
Tantric
That won't work at all. If you want to "slow down" you can try sleep() or usleep(). But this still wouldn't help you with what you're trying to do.
Funny, I've gotten it work in some of my past games. Usually 150 ends up being some insane number though, but it definitely works.

My guess would be, that some compilers might optimize
for(int pause = 0; pause < 150; pause++)
to do nothing.

Re: Switch-Case inputs

Arikado — Mon, 15 Dec 2008 17:32:21 +0100

Quote
Tantric
That won't work at all. If you want to "slow down" you can try sleep() or usleep(). But this still wouldn't help you with what you're trying to do.

Funny, I've gotten it work in some of my past games. Usually 150 ends up being some insane number though, but it definitely works.

Better suggestion though:

while(wiimotes are not initialized){

}

Not sure what wiimotes not initialized would be I don't have libogc in front of me at the moment. There is something for it though.

Re: Switch-Case inputs

daniel_c_w — Mon, 15 Dec 2008 14:28:56 +0100

I have no environment to test it and I find no WPAD documentation, but
doesn't any of the functions like WPAD_GetStatus() give you the value of connected Wiimotes?

Your program could wait, until it's > 0.

Re: Switch-Case inputs

SpaceJump — Mon, 15 Dec 2008 08:02:55 +0100

Any other idea how I can archieve this?

Re: Switch-Case inputs

henke37 — Mon, 15 Dec 2008 07:30:36 +0100

Solving timing issue by adding a random delay is not the solution.

Re: Switch-Case inputs

Tantric — Mon, 15 Dec 2008 03:55:21 +0100

Quote
Arikado
WPAD_Init();

for(int pause = 0; pause < 150; pause++){

}

//Check for button press
Try this, it'll slow everything down for a tiny bit. Modify 150 if necessary.

That won't work at all. If you want to "slow down" you can try sleep() or usleep(). But this still wouldn't help you with what you're trying to do.

Re: Switch-Case inputs

Arikado — Mon, 15 Dec 2008 00:55:47 +0100

WPAD_Init();

for(int pause = 0; pause < 150; pause++){

}

//Check for button press

Try this, it'll slow everything down for a tiny bit. Modify 150 if necessary.

Re: Switch-Case inputs

SpaceJump — Mon, 15 Dec 2008 00:30:59 +0100

Because when the app loads I want it to do something when no button is being held, and something else if button A is held.

Re: Switch-Case inputs

comex — Mon, 15 Dec 2008 00:20:05 +0100

Quote
SpaceJump
[basically I want to check if a certain button is help when the program is loaded]

Why exactly do you want to do this?

Re: Switch-Case inputs

SpaceJump — Mon, 15 Dec 2008 00:10:42 +0100

WPAD_init is the first function I call, and directly after the call I want to check if a button is held [basically I want to check if a certain button is help when the program is loaded]. But upon loading the app I see that the Wiimote flashes to late and the point of the button check is already past.

Re: Switch-Case inputs

henke37 — Sun, 14 Dec 2008 22:21:35 +0100

What I think they are trying to say is that the function is blocking and will not return until the job is done.

Re: Switch-Case inputs

Tantric — Sun, 14 Dec 2008 22:18:17 +0100

WPAD_Init() should be the first thing you do (unless you want DVD, in which case DI_Init() should happen first). Assuming you run it this early, your program shouldn't have to wait.

Re: Switch-Case inputs

Arikado — Sun, 14 Dec 2008 22:13:22 +0100

Unless your using some sort of a thread, your program SHOULD not do anything until initialization is complete.

Re: Switch-Case inputs

SpaceJump — Sun, 14 Dec 2008 21:27:44 +0100

When I call WPAD_Init(); to initialise the Wiimote, how can I make my program wait until initialising is finished?

Re: Switch-Case inputs

SpaceJump — Fri, 12 Dec 2008 16:00:08 +0100

I want to them to have a different effect (one button held at a time).

Thanks for your answers.

Re: Switch-Case inputs

daniel_c_w — Fri, 12 Dec 2008 15:22:30 +0100

@SpaceJump:
When 2 buttons are pressed do you want them to have the same effect as if they were pressed separately?
(example: A: shoot, B: jump, A+B: shoot and jump)

Then use a lot of IFs in the right places. Check for the A button where it makes sense in your code, and check for the B button, where it makes sense.

Or do you want them to have a different effect?
(example: A: shoot, B: jump, A+B: open menu)

Then use whodare's code examples.

Re: Switch-Case inputs

whodares — Fri, 12 Dec 2008 13:35:10 +0100

 switch( buttonsHeld )
 {
  case WPAD_BUTTON_1:
   break;
  case WPAD_BUTTON_2:
   break;
 }

Edit: D'oh sorry, that will only work if only 1 button is down at a time...

Edit 2: You can't do a switch if there's the possibility of several outcomes. If the user presses 1 and 2, unless you add

  case WPAD_BUTTON_1 | WPAD_BUTTON_2:
   break;

Switch-Case inputs

SpaceJump — Fri, 12 Dec 2008 13:27:26 +0100

I want to read an Wiimote input (a held button):

u16 buttonsHeld = WPAD_ButtonsHeld(0);

Now I know how to read what button is being held with if:

if (buttonsHeld & WPAD_BUTTON_A ) { 
        printf("Button A is being held down.\n");
}
else {
  if (buttonsHeld & WPAD_BUTTON_1){
	printf("Button 1 is being held down.\n");
  }
}

How can I read what button is held with a Switch-Cause statement?

Thanks in advance,
SJ