@a1ex
In the script I'm playing with I wish to hijack the SET and UNPRESS_SET keys, so I can use these with a long press, ie use normally if the press/unpress is less that x seconds, or use differently if longer than x seconds.
All is OK, other than the ETTR remains triggered by a SET, no matter what I do.
That is, the ETTR triggered by SET seems to circumvent the key event handler, eg if I use the following, ETTR still triggers off of SET:
if kk == KEY.SET or kk== KEY.UNPRESS_SET then
return false
end
Is this intentional or a 'bug'?
Cheers
Garry