How about adding an optional i-time argument to sensekey to
request the new behavior, defaulting to the old one for
compatibility ? Also, if the host implements the replacement
by overriding the opcode, rather than useing csoundKeyPress(),
the limitations of range (0 to 255) and only one event per
control period are avoided.

On Thursday 08 June 2006 23:41, matt ingalls wrote:

> well on 2nd thought, it could break existing orcs if they are just  
> using sensekey as a trigger and not looking at the actual char
> returned... 


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