kanyun157 / giimote

Automatically exported from code.google.com/p/giimote
GNU Lesser General Public License v3.0
0 stars 0 forks source link

C and Z buttons are the same as A and B #6

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
C and Z buttons are the same as A and B.  When checking these two buttons C
will turn on when you press A and Z will turn on when you push B.  This is
caused by the constants:
wm_a=0
wm_b=1
wm_c=0
wm_z=1

Please change it to work with the correct buttons on the numchuck

Thanks,
Hieros

Original issue reported on code.google.com by Sirwin...@gmail.com on 2 Apr 2008 at 2:41

GoogleCodeExporter commented 8 years ago
Thank you, this has been noted and will be corrected in the next release.

Original comment by leif902 on 2 Apr 2008 at 1:42

GoogleCodeExporter commented 8 years ago
This has been fixed in revision 96 of the source. Issue will be closed upon next
official release.

Original comment by leif902 on 2 Apr 2008 at 2:39

GoogleCodeExporter commented 8 years ago
Thanks for fixing that.  I really like this project.

Thanks again,
Hieros

Original comment by Sirwin...@gmail.com on 2 Apr 2008 at 6:16

GoogleCodeExporter commented 8 years ago
I would like to apologize for posting this issue.  I stupidly looked over the 
fact
that there is a wm_nunchuck_check_button, not just a wm_check_button.  I feel 
like a
complete idiot.  Thank you for helping anyways.

Hieros

P.S.  While I'm here I might as well ask.  How often can you call a function to 
check
all of the buttons (and joystick and other stuff)?  25 calls per step * 30 
steps =
750 calls per second.  Will all of these interrupts bog down the wiimote, the 
game,
or both?  Also how fast would this drain the battery? Thanks

Original comment by Sirwin...@gmail.com on 2 Apr 2008 at 8:48

GoogleCodeExporter commented 8 years ago
That's fine, but it will now return the proper error and make things that much
easier, so this was a good bug report :)

As for your question, please ask questions on the GMC topic in the future or 
email
me. However, since it's already here... Game Maker does not update the buttons,
joysticks, accelerometers, etc. Inside GiiMote there is a special event which 
does
this only when the Wii Remote is updated which is about 100 times per second 
unless
the user does it manually. You can call a function to check a button as many 
times as
you want and it won't change anything, it is simply reading the stored value. 
The
only functions which will bog down your bandwidth if called to much are 
wm_update
which updates the entire status of the Wii Remote by communicating with the WM 
over
blue tooth and wm_get_battery which calls wm_update. In the future please ask
questions over the GMC though :) thanks.

Original comment by leif902 on 2 Apr 2008 at 8:56

GoogleCodeExporter commented 8 years ago

Original comment by leif902 on 11 Jun 2008 at 9:03