From: Joe Krahn <krahn@ni...> - 2006-09-21 23:18:03
I'm working to include general XINPUT device support, which overlaps the
Joystick stuff, so I would like to clean that up as well. My design
questions involve what to do about multiple joysticks, and extended
joystick events (beyond axes x,y,z).
In general, I dislike the current multi-joystick functions. I think it
is a better GLUT-oriented design to only two functions instead of the
current collection: glutSetJoystick() and glutGetJoystick(). All other
joystick functions work as usual, but on the current joystick instead of
joystick zero. Is this a good plan for the next release?
Also, I think joystick functions for calibration should be removed from
the API, right? Ideally calibration should be managed by the OS. In
cases where it cannot be done, a config file can be used. But, this does
not require mucking up the API with such things. Good?
Lastly, how to handle extra axes without deviating too much from the
standard GLUT API. Maybe they could query-only values by adding
glutDeviceGet enums, and avoid adding extra callback functions.
I thought that FreeGLUT wanted to stick to the GLUT API, but several
extended functions have already gotten in. If they are going to be
allowed, I think it could be done better than what's already there.
Get latest updates about Open Source Projects, Conferences and News.