General
Pads: preventing accidental presses?
Started by Ozymandias on .
Sign in or create an account to join the conversation.
Hi all,
I'm using a Pads object with the following OSC output, where the address of each pad is taken from a string array (v):
Thanks for any help.
I'm using a Pads object with the following OSC output, where the address of each pad is taken from a string array (v):
//On Expression: x goes from 0 to positive
oscout(0,'/'+v[firstof(x)],1);
Everything works as expected. The trouble is I'm using them to trigger DAW actions, so, if I happen to touch a neighboring pad I can trigger unwanted actions. How can I prevent additional messages being sent whilst one pad is already held?Thanks for any help.
so you want to have it that while you are touching one pad, no other pad can send out data correct?
if so, here is a pad lock. I didn't think about too quickly, so maybe there is a better way. You could also show/hide a no touch canvas on the press and release of x, anyway this is a different way using an expression as a gate.
hope this is what you wanted, let me know.
padLock.jzlib
if so, here is a pad lock. I didn't think about too quickly, so maybe there is a better way. You could also show/hide a no touch canvas on the press and release of x, anyway this is a different way using an expression as a gate.
hope this is what you wanted, let me know.
padLock.jzlib
That's perfect, ndivuyo - thank you!