joystick calibration process and interface poorly documented
Bug #497835 reported by
Emmet Hikory
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| joystick (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: joystick
The behaviour of a given joystick before and after calibration is not documented well for either developers or end-users. As a result, it is hard to know if a given joystick has been calibrated correctly, or is indeed even producing correct values.
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in joystick (Ubuntu): | |
| status: | New → Fix Released |
To post a comment you must log in.
This bug was fixed in the package joystick - 20051019-12
---------------
joystick (20051019-12) unstable; urgency=low
* Use the correct maximum number of axes. LP: #595767.
* Small fixes to the manpages.
* Correct all remaining ioctl() checks. Closes: #587439.
* Explain the purpose of calibration and how to determine whether a
joystick is calibrated. LP: #497835.
* Standards-Version 3.9.0: use Breaks rather than Conflits, and
incidentally move the Breaks on dvb-utils to evtest where it really
belongs.
-- Alessio Treglia <email address hidden> Sun, 11 Jul 2010 00:13:43 +0200