Currently Axis range is implemented however the underlying driver delivers it and is complemented with a min/max value.
All (?) uses of an absolute axis I can think of involve normalizing the axis value to -1.0/1.0 or 0.0/1.0 - Aircraft bank flaps -->( y_axis.value / (y_axis.max - y_axis.min) ) * flap_range_of_motion - Painting with tablet --> (y_axis.value / (y_axis.max - y_axis.min) ) * window.width - Generalized axis/axis mapping -> ( (axis.value / (axis.max - axis.min) + offset1) * target_range + offset2 I'm far from infallible, but if all sensible uses of an absolute axis involve "axis.value / (axis.max - axis.min)", shouldn't the wrapper do this by default (and offering the raw_value perhaps as axis.raw_value? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en -~----------~----~----~----~------~----~------~--~---
