On Friday 09 June 2006 15:35, matt ingalls wrote:

> On Jun 9, 2006, at 4:47 AM, Istvan Varga wrote:
> 
> > as if the key was only pressed for a very short time), and it is
> > expected that host applications like MacCsound will replace it with
> > their own platform specific implementation.
> 
> i don't think there is anything platform-specific to do inside the  
> opcode, i would probably just make key numbers > 127 be "off" keys,
> which then doesn't seem like a strong case to even change the opcode
> at all.
> 
> unless you are thinking the opcode and host would be talking to  
> eachother directly, not through the API?   even so, that might not
> be possible in my case because i cannot #include csdl.h because it
> #includes sndfile.h which causes compile errors in codewarrior.

That is what I have thought of, but if limiting the number of possible
key codes to 127 (which is actually less because many are redundant
due to upper/lower case letters etc.) is not a problem, it is indeed
easy to reinterpret codes >= 128 as key release events in the API.
If using csoundKeyPress(), the host should pay attention to correctly
buffering the events, and not sending more than one per control period.


_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net