<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Quoth IOhannes m zmoelnig, on 21/04/2012 14:23:
<blockquote cite="mid:4F92B4C9.1060103@iem.at" type="cite">
<pre wrap="">-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 2012-04-18 20:27, Andrew Faraday wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I've had this problem before with [hid], apparently it's a hardware
issue called 'debouncing', which is often ignored because it is often
irrelevant (pushed is pushed, for game controllers, rather than a
button-on/button-off signal used for most music systems).
You can deal with the problem in pure data by using a trigger, float and
delay of one millisecond. See the attached patch, click the message
boxes and watch your terminal for the result.
</pre>
</blockquote>
<pre wrap="">
[change] seems to be the more appropriate solution here...
fgmasdr
IOhannes
</pre>
</blockquote>
<br>
Thanks for the suggestion. The problem I have with these two
solutions is that they only work when the double triggers are in
sequence. Sometime they arrive like this:<br>
<br>
<tt>[hid] 0.7, written by Hans-Christoph Steiner <a
moz-do-not-send="true" class="ecxmoz-txt-link-rfc2396E"
href="mailto:hans@eds.org"><hans@eds.org></a><br>
compiled on Apr 15 2012 at 08:12:47 <br>
[hid] opened device 4 (/dev/input/event4): AT Translated Set 2
keyboard<br>
</tt><tt>print: key key_j 1<br>
print: key key_l 1<br>
print: key key_j 1<br>
print: key key_l 1<br>
print: key key_j 0<br>
print: key key_j 0<br>
print: key key_l 0<br>
print: key key_l 0<br>
<br>
</tt>So I would need to store the value of each key individually and
check each one with [change].<br>
Instead of this long-winded method, I've downloaded [linuxevent]
which is working nicely so I think I'll stick with this even though
it may be deprecated?<br>
<br>
Surely this is a bug with [hid] though?<br>
<br>
James<br>
</body>
</html>