Closed GoogleCodeExporter closed 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
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
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
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
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
Original comment by leif902
on 11 Jun 2008 at 9:03
Original issue reported on code.google.com by
Sirwin...@gmail.com
on 2 Apr 2008 at 2:41