Audio Triggering + Mouse Event latency

Scott Rossi scott at tactilemedia.com
Tue Nov 16 02:20:30 EST 2010


Ah, OK, that's definitely a different implementation than a keyboard.

Only a few other options I can think of for the mouseDown message:

1) Trapping mouseDown in a frontScript, which gets executed before any
mouseDown events in a button/card/stack.  Have you already tried this?

2) Not ideal from a processor use standpoint, but using mouse polling in a
tight repeat loop, ie:
 on trackClicks
   if the mouse is down then playMySound
   send "trackClicks" to me in 10 millisecs
 end trackClicks

3) Using a wait command, which is better than the above in terms of
processor use, but harder to manage:
 on trackClicks
   wait while (the mouse is up) with messages
   playMySound
   send "trackClicks" to me in 0 millisecs
 end trackClicks

The above is a bit like a repeat loop that waits for a condition -- the
benefit is it doesn't impact processor use like a standard repeat loop, the
drawback is, it's harder to get out of (might need a frontScript or
similar).

Regards,

Scott Rossi
Creative Director
Tactile Media, UX Design


Recently, Anthony Howe wrote:

> Hiya Scott,
> 
> Yea.. the mouseDown on a virtual instrument for a user is difficult in a
> desktop computing scenario for sure.
> 
> We're different here though...I can't remember if I already specified this,
> but the target user scenario is aimed at students 'tapping' on an interactive
> whiteboard with their finger or stylus to play the instruments.
> 
> In this implementation, the mouseDown event would be the ideal event to
> handle. It would be MUCH more intuitive for the user (lots of students in a
> classroom) to simply be able to trigger the events directly from the
> interactive whiteboard, and not be worried about what key to press to activate
> what instrument etc...
> 
> Having said that, we're now putting some more thought into how to make best
> use of the keyboard as the 'playing surface' of the instrument, given that the
> mouseDown event does not look like it's going to work out reliably....hope I'm
> wrong!
> 
> Cheers,
> 
> A._______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution





More information about the use-livecode mailing list