On Sun, 09 Aug 2009 09:33:50 -0700, Josh Triplett <[email protected]>
wrote:
> Saving and restoring joystick calibration in an init script doesn't make
> sense. It assumes that the joystick remains attached when shutting
> down, remains attached when booting up, and (in the case of multiple
> joysticks) always gets assigned to the same js device.
It made sense to me at the time, because the package has to cater for
different varieties of joysticks, not just USB devices! I do realise it isn't
perfect, and I was working on some mechanism to store calibration data other
than by device name. I also hadn't reckoned on so many users connecting and
disconnecting their joysticks regularly, but that is rather short-sighted of
me.
> Instead, how about providing a udev script? On joystick insertion,
> check for a file
> "/etc/jscal/$env{ID_BUS}-$env{ID_SERIAL}-$env{ID_CLASS}", and if present
> run jscal with it. The user can store calibration data there manually,
> or you could provide some script to do so automatically for a given
> joystick (something like "jscal-persistent").
Something like that would work for a fair amount of USB joysticks, thanks.
Could you send me the output of
/sbin/udevadm info -a -p $(/sbin/udevadm info -q path -n /dev/input/js0)
with your joystick connected?
Regards,
Stephen
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
