If you use pd-l2ork v.1 (pre-Purr-Data) it also offers an optional
argument for key and keyname objects (arg 1, e.g. [key 1]) that allows
for filtering of repeat events. Doing so is fairly tricky given the
tcl/tk + networked gui communication implementation, particularly on
Linux, but it does work. Porting it should not be too difficult.
Best,
Ico
On 3/18/2019 1:01 PM, katja wrote:
One workaround (that I'm using in practice since long) is to hold back
the keyup message for slightly longer than the repeat time, and only
let it through when keydown didn't come again in the meantime. The
method introduces latency on keyup but not on keydown. See attached
patch, it is slightly too complicated for ASCII illustration.
Katja
On 3/18/19, Peter P. <[email protected]> wrote:
Hi list,
chiming in to the discussion of possible improvements regarding mice and
now also keyboards, I am wondering if there could be a way within Pd to get
keyboard events without having the operating systems (all three of them)
repeat key down/up events in rapid succession.
I know that I can tell the operating systems to disable it but would
absolutely prefer Pd's keyboard objects to get these without repeats.
Happy to hear any feedback on that!
P
_______________________________________________
[email protected] mailing list
UNSUBSCRIBE and account-management ->
https://lists.puredata.info/listinfo/pd-list
_______________________________________________
[email protected] mailing list
UNSUBSCRIBE and account-management ->
https://lists.puredata.info/listinfo/pd-list
_______________________________________________
[email protected] mailing list
UNSUBSCRIBE and account-management ->
https://lists.puredata.info/listinfo/pd-list
