Sounds like a good idea. If dispatch is already fast, a timer would just allow you to slow it down.
BTW, I believe using quotes should make your message "send"-able. send "clearVideo LayerAlpha, baseLayer, LayerGraphic, LayerAudio" to me in 700 milliseconds Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design On 8/26/14 7:09 PM, "Richard Gaskin" <[email protected]> wrote: >I love "dispatch", and the more I use it the more I find "send" murky. > >With "dispatch" params seem more natural to me: > > dispatch "somecommand" to tSomeObj with tArg2, tArg2 > >But with "send" it's less clear how params are handled - here's an >example from the forums today: > > send clearVideo LayerAlpha, baseLayer, LayerGraphic, \ > LayerAudio to me in 700 milliseconds > >Seems like a good guess as to how it should be used, but of course the >compiler complains. > >So given that "dispatch" is also faster, why not use it for everything, >extending it with "in" to allow timers: > > dispatch "somecommand" to tSomeObj with tArg2, tArg2 in 2 secs > >Is there some reason I've overlooked as to why "send" allows timers but >"dispatch" doesn't? > >-- > Richard Gaskin > Fourth World Systems > Software Design and Development for the Desktop, Mobile, and the Web > ____________________________________________________________________ > [email protected] http://www.FourthWorld.com > >_______________________________________________ >use-livecode mailing list >[email protected] >Please visit this url to subscribe, unsubscribe and manage your >subscription preferences: >http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
