Opened 16 years ago
Last modified 16 years ago
#59 assigned defect
Wiiremote redetection problem
Reported by: | Florian Roth | Owned by: | nobody |
---|---|---|---|
Priority: | trivial | Milestone: | MS4: Future extensions |
Component: | controller | Version: | |
Keywords: | Cc: |
Description
Currently you cannot scan for new Wiiremotes connected to the Bluetooth
Stack during Jacavi is running. Its also not possible to Rescan Wiimotes if one or more Wiiremotes are out of reach or turned of.
Change History (15)
comment:1 Changed 16 years ago by
Status: | new → accepted |
---|
comment:2 Changed 16 years ago by
Component: | unspecified → controller |
---|---|
Priority: | major → trivial |
comment:3 follow-up: 4 Changed 16 years ago by
Technical expertises
- I figgured out that the reconnection problem is a bug in the WiiuseJ API see
reconnection problem in wiiusej users
- With the onDisconnectionEvent of the WiiUseJ API we could remove an not available or disconnected Wiimote from the InputDeviceManager?. Fact is there is a bug in wiiuse (C) so wiiuseJ has the same problem. We have to wait for the new version. see onDisconnectionEvent() WiiuseJ users group
- Dissable all log messages from WiiUseJ API. Iam on this it has to do with the underlaying native wiiuse API (written in C). Iam on this right now
comment:4 follow-up: 5 Changed 16 years ago by
Replying to froth:
Technical expertises
- I figgured out that the reconnection problem is a bug in the WiiuseJ API see
reconnection problem in wiiusej users
- With the onDisconnectionEvent of the WiiUseJ API we could remove an not available or disconnected Wiimote from the InputDeviceManager?. Fact is there is a bug in wiiuse (C) so wiiuseJ has the same problem. We have to wait for the new version. see onDisconnectionEvent() WiiuseJ users group
- Dissable all log messages from WiiUseJ API. Iam on this it has to do with the underlaying native wiiuse API (written in C). Iam on this right now
comment:5 Changed 16 years ago by
Replying to froth:
Replying to froth:
Technical expertises
- I figgured out that the reconnection problem is a bug in the WiiuseJ API see
The same problem exists under Ubuntu
- With the onDisconnectionEvent of the WiiUseJ API we could remove an not available or disconnected Wiimote from the InputDeviceManager?. Fact is there is a bug in wiiuse (C) so wiiuseJ has the same problem. We have to wait for the new version. see onDisconnectionEvent() WiiuseJ users group
This is not a problem in Ubuntu
- Dissable all log messages from WiiUseJ API. Iam on this it has to do with the underlaying native wiiuse API (written in C). Iam on this right now
Same Ubuntu
comment:6 follow-up: 7 Changed 16 years ago by
comment:7 Changed 16 years ago by
Replying to hheimbuerger:
FYI, even restarting JaCaVi doesn't get rid of the Wiimote here.
I can:
- Start JaCaVi without a connected Bluetooth adapter.
- Click 'redetect' --> no Wiimote appears.
- Plug the Bluetooth adapter in.
- Click 'redetect' --> Wiimote 1 appears.
Note that my Wiimote is deactivated during the whole process.
Nevermind, you already knew that. It's the same effect we had when you started a detection during the last meeting and it displayed the Wiimote you left at home.
comment:8 Changed 16 years ago by
When working on this, please remember that the input device configuration dialog can still have bugs. I'm not sure it properly throws missing devices away, etc.
If you at some point think it should work, but the input device configuration dialog shows unexpected behaviour, make sure the bug is not in the dialog.
comment:9 Changed 16 years ago by
comment:10 Changed 16 years ago by
The developer of WiiuseJ said that there will be a new build with redetection fix soon
comment:11 Changed 16 years ago by
comment:12 Changed 16 years ago by
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
Tested with two Wiiremotes. Works fine.
comment:13 Changed 16 years ago by
Milestone: | MS1: First release (1.0.0) → MS4: Future extensions |
---|---|
Resolution: | fixed |
Status: | closed → reopened |
Works for Windows not for Linux. Its a WiiuseJ Problem.
comment:14 Changed 16 years ago by
comment:15 Changed 16 years ago by
Owner: | changed from Florian Roth to nobody |
---|---|
Status: | reopened → assigned |
Version: | pre-1.0 |
Under Linux there is still a redetection problem for Wiiremotes. In my opinion this has to do with a bugy WiiUseJ and inderect with the several Bluetooth Stacks Win / Linux.
AT this time I have the following Problems because of bugs in the WiiUseJ API also reported in WiiUseJ Group
I tested on Windows XP SP3 OS.