-
paralizer changed the public information on the wiiuse project.
2010-01-04 18:37:41 UTC by paralizer
-
paralizer changed the public information on the wiiuse project.
2010-01-04 18:37:41 UTC by paralizer
-
paralizer changed the public information on the wiiuse project.
2010-01-04 18:37:37 UTC by paralizer
-
paralizer changed the public information on the wiiuse project.
2010-01-04 18:37:37 UTC by paralizer
-
paralizer changed the public information on the wiiuse project.
2010-01-04 18:37:37 UTC by paralizer
-
Setting WIIUSE_CONTINUOUS does correctly tell the Wiimote to generate events continuously. However, if no state changes occurred, then the propagate_event function will not set the wm's event:
if (state_changed(wm))
wm->event = WIIUSE_EVENT;
This contradicts the documentation, which says:
"By enabling this flag then wiiuse will constantly generate events even if the status of the...
2009-11-24 17:29:27 UTC by ttencate
-
I too had this issue and traced the problem to io_nix.c and the value of l2_cid not being initialized properly. I added an explicit initialization and everything worked after that. I created a patch file that can be viewed here:
http://gist.github.com/241910
Cheers,
Dan Wanek.
2009-11-24 14:42:17 UTC by zenchild
-
Using wiiuse v0.12, by the way.
2009-11-24 12:06:09 UTC by ttencate
-
The Windows implementation of wiiuse never sends the WIIUSE_UNEXPECTED_DISCONNECT event. In fact, there is no code in the Windows implementation that sends that event at all. Upon ERROR_HANDLE_EOF and ERROR_DEVICE_NOT_CONNECTED from ReadFile, a normal disconnect event is sent.
However, these errors don't seem to happen on my system. Instead, if I disconnect the Wiimote, wiiuse_io_read just...
2009-11-24 10:23:32 UTC by ttencate
-
If you try to disable ir before the connection is established, the request is treated as 'enable ir' and executed later. This patch fixes it.
2009-11-03 12:19:40 UTC by jasager
