On Mon, Oct 24, 2011 at 14:24, Chris Friesen <chris.friesen@xxxxxxxxxxx> wrote: > On 10/22/2011 05:42 AM, Denilson Figueiredo de Sá wrote: > >> It may even happen to send an out-of-range value for one axis, but a >> valid value for another axis. The code should be prepared for that >> (ignore one, but keep the other). > > In this case what should be used for the "invalid" axis value? The previous > value? If that's an absolute pointing device, can we supply only one axis? I mean, can we do this: "move the pointer to this X position, but leave the Y position where it currently is". (note that the pointer might have moved since last input from this device, due to other devices also being present) If that's not possible, then I'm not sure about what should be the correct behavior. Should we ignore both axes if one of them is invalid? Should we use the last good value from the other axis? (note that relative pointing devices like proper mice shouldn't have this issue, as we can just use zero for invalid values, which means "no movement") I haven't tested that on Windows (yet), so I don't know how it behaves. If I test it, I'll post my results here. I know, this is a corner case difficult to decide about. By the way, my report was about absolute pointing devices, but I haven't tested how Linux USB HID behaves for other kinds of devices (keyboards, gamepads, anything else). -- Denilson Figueiredo de Sá Rio de Janeiro - Brasil -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
