Ah yes, this is an annoyance with many USB HIDs that output relative data. The data they output is in effect speed, but they don't output zero. What those devices are actually outputting is the amount of change in pixels since the last measurement of location. If there is no change, they output
Absolute value. So if the last value was -3 and the mouse stop moving, it stays
there. What I meant was that if the number was greater than absolute value of
1, and the mouse stops, it stays there. I put abs(1) because the sign is
logical. If I move from right to left it stays in a negative numb
I read your question again, and I don't quite get it. What's abs(1)?
.hc
On Jul 24, 2007, at 4:37 AM, Diego Azar wrote:
Hans, thanks for your reply. I'm working with hidio because it
works better, with my configuration, than the hid.
thanks again, Diego.
Hans-Christoph Steiner <[EMAIL PR
Hans, thanks for your reply. I'm working with hidio because it works better,
with my configuration, than the hid.
thanks again, Diego.
Hans-Christoph Steiner <[EMAIL PROTECTED]> wrote:
First off, I must say [hidio] can be quite rough since it's very alpha. But I
am glad to have people testi
First off, I must say [hidio] can be quite rough since it's very
alpha. But I am glad to have people testing it, with that in mind.
But if you are using [hidio] and not [hid], and you are getting
"rel_x" as a message, then that is a bug. "rel_x" is the old [hid]
style messages. [hidio]
Hi. I'm using the hidio object with a mouse and it seems there's something I'm
not getting. The problem is when routing the list from the rel_x to obtain the
x relative axes; the value, sometimes, is greater than abs(1) when the mouse is
not moving. Is this behavior correct? Is this a bug? Has i
