Seems right to me. Dispatch looks for a handler in the script you are dispatching to. You would have to have a handler called ON BEEP which would be illegal and wouldn't compile because BEEP is a reserved word. Try using send instead.
Bob On Dec 22, 2010, at 9:56 AM, Richard Gaskin wrote: > David Bovill wrote: > >> Anyone got a reason for this being Appropriate behavior? >> >> dispatch "beep" to this cd -- no beep >>> send "beep" to this cd -- a beep > > Interestingly, running this in the Message Box: > > dispatch "beep" to this cd; put it > > ...yields "unhandled" > > You get the same with any build-in command, e.g.: > > dispatch "go next" to this cd; put it > > Whether this is a weakness in the engine or the documentation is a question > of intention: > > Is "dispatch" designed to handle only custom handlers? It appears to be, and > if that's what's intended it's working fine and all that's needed is a note > in the docs clarifying that. > > But if the intention was that it could be used for built-in commands too then > there appears to be a bug in the engine. > > -- > Richard Gaskin > Fourth World > LiveCode training and consulting: http://www.fourthworld.com > Webzine for LiveCode developers: http://www.LiveCodeJournal.com > LiveCode Journal blog: http://LiveCodejournal.com/blog.irv > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
