Katja, I am trying to use your idea about holding back key ups. However it seems that [keyup] outputs 0 for letter keys, and numbers for the number keys. I can't seem to figure out why. But it has the consequence that your nice idea will possibly not work if two or more keys are held down together. Seems this one is not (yet) solved for me.
Thanks again! P * katja <[email protected]> [2019-03-18 18:09]: > 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
