{5} Assigned, Active Tickets by Owner (Full Description) (5 matches)
List tickets assigned, group by ticket owner. This report demonstrates the use of full-row display.
dsmith
| Ticket | Summary | Component | Milestone | Type | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #31 | Wiimote discover problem | libcwiid | Version 0.6.00 | defect | 04/12/07 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
For some people, automatic wiimote discovery never works. For more details, see:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #53 | Need some way to discover and connect to remotes with shorter timeouts, or asynchronously | libcwiid | defect | 01/04/08 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
wiimote_open takes a long time to find and connect to a new Wiimote, which involves some very long delays (particularly when using 1+2 rather than the sync button). However, I want to connect several Wiimotes without knowing the number of Wiimotes or their bluetooth addresses in advance; I will use something like "Press A on any remote to stop looking for more remotes". I don't see any way with the current cwiid interfaces to do this elegantly. First, even if I had the bluetooth addresses (such as from the cwiid bluetooth discovery functions), cwiid_open still takes a long time to connect. While connecting, I cannot watch for the A button on other remotes and abort. I also cannot discover and connect to new wiimotes in parallel, so the long timeouts run sequentially rather than concurrently. Second, the bluetooth discovery functions themselves appear to have some long timeouts. (If I have missed some other way to do this, my apologies; please let me know.) |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #1 | Audit all error checking | other | Version 1.0 | task | 03/13/07 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Audit the error checking, especially in libwiimote. Probably going to use a header I've been working on similar to Rochkind's error checking from "Advanced Unix Programming" that implements basic error handlers and more concise error checking syntax. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #19 | Xlib error | wmgui | Version 1.0 | defect | 04/03/07 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
I've gotten strange X errors twice while running wmgui, the second one was: Xlib: unexpected async reply (sequence 0x1f8b)! This came up right after an error message window from libwiimote, so I suspect it's some sort of multithreading issue involving dead threads that own windows. Solution is probably to not to use a wiimote_err function that opens a window - either queue errors to be displayed, or print them on the command line. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #48 | Python-devel required, but configure doesn't check. | build system | Version 0.6.00 | defect | 09/27/07 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
I tried compiling cwiid-0.6.00 on an openSUSE 10.2 system and found that the configure script did not check for python-devel ("Include Files and Libraries Mandatory for Building Python Modules"), even though it is required. This of course meant that the build failed. This wasn't a problem as I just installed it and then everything compiled OK, but I thought maybe this should be fixed. The errors started with: gcc -g -Wall -W -DHAVE_CONFIG_H -I/home/pt/CWiid/cwiid-0.6.00/common/include -I../libcwiid -DWMINPUT_CONFIG_DIR=\"/usr/local/etc/cwiid/wminput\" -DCWIID_PLUGINS_DIR=\"/usr/local/lib/cwiid/plugins\" -I/usr/include/python2.5 -c -o py_plugin.o py_plugin.c py_plugin.c:38:20: error: Python.h: No such file or directory py_plugin.c:45:26: error: structmember.h: No such file or directory py_plugin.c:56: error: expected specifier-qualifier-list before ‘PyObject’ py_plugin.c:62: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token py_plugin.c:63: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token py_plugin.c:64: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token py_plugin.c:65: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token py_plugin.c:66: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token py_plugin.c:68: error: expected declaration specifiers or ‘...’ before ‘PyObject’ py_plugin.c:69: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token py_plugin.c:83: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘Module_Methods’ py_plugin.c: In function ‘py_init’: py_plugin.c:92: error: ‘PyObject’ undeclared (first use in this function) py_plugin.c:92: error: (Each undeclared identifier is reported only once py_plugin.c:92: error: for each function it appears in.) etc, etc. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
