Hello, Apologies if this specific issue has been discussed before. I searched the archives and found related topics, but not this issue.
I’d just like to find out if what I’m seeing on my machine is happening at large. On latest macOS (10.13.3), with Pd 0.48-1, keyup and the keyup functionality of keyname appear broken, with the following behavior: (The quick and easy way to observe this is to open key-help.pd, then type. If your situation is like mine, you will never see the status outlet of keyname report an output of 1.) Pressing a key on my keyboard produces the expected response from key, but also produces an instantaneous response from keyup and from the status outlet of keyname (even though the key has not been released). That is, if I follow the status outlet of keyname with [sel 0 1], routing the bang from 1 to the left inlet of timer, and the bang from 0 to the right inlet of timer, then pressing and holding any key returns either a time of 0 between keyname’s issuance of the values 1 and 0, or a period reflecting the blocksize (1.45125); in either case, the keyup is issued long before the OS decides to start issuing key repeats. Actually, complicating this issue is this: regardless of whether System Preferences > Keyboard > Key Repeat is set to Off or on (any other value), Key Repeat does not appear to /ever/ occur in any application except Pd, and yet it will /always/ occur in Pd (but only for keyboard characters which can evoke alternate characters, i.e. ‘a’, which can evoke à, á, â, ä, æ, ã, å, or ā when held during text input in most apps except Pd). So, is the issue (keyup firing on key press) occurring for others, and if so, is it just Mac users, or does it occur cross-platform? Best regards, Kevin _______________________________________________ Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
