Let me put it differently: Send generates a system message. Any system message.
Dispatch calls a handler optionally with parameters. Make sense?
Bob
On Dec 22, 2010, at 9:40 AM, David Bovill wrote:
> Anyone got a reason for this being Appropriate behavior?
>
> dispatch "beep" to this cd -- no
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:
>
On Dec 22, 2010, at 12:56 PM, 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
...y
I'd say it's a bug?
On 22 December 2010 17:56, 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:
>
I've noticed that the message box world has been little strange for some
commands.
In the past, answer "Prompt" in the msg box would
*not*show the dialog
but answer "Prompt"; put it *
does* show the answer dialog
I have not checked t
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
Anyone got a reason for this being Appropriate behavior?
dispatch "beep" to this cd -- no beep
> send "beep" to this cd -- a beep
>
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage you
