Dispatch and send

[stephen barncard]

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 this since 4.0

sqb

On 22 December 2010 11:56, Richard Gaskin <ambassador at fourthworld.com>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 at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>



-- 



Stephen Barncard
San Francisco Ca. USA

more about sqb  <http://www.google.com/profiles/sbarncar>