Dispatch-Sending keyDown

[Jan Schenkel]

One of the key differences between 'send' and 'dispatch' (other than the 'with' extension to more easily pass paramaters), is that 'dispatch' won't throw an error if the message isn't handled.

So in fact, when you use
##
dispatch "foo" to this stack with "bar"
##

It internally works more like
##
try
  put "bar" into theParam
  send "foo theParam" to this stack
catch theError
  -- ignore the error but set the result to "unhandled"
end try
##

I hope this clarified it somewhat.

Jan Schenkel
=====
Quartam Reports & PDF Library for Revolution
<http://www.quartam.com>

=====
"As we grow older, we grow both wiser and more foolish at the same time."  (La Rochefoucauld)


--- On Mon, 10/26/09, DunbarX at aol.com <DunbarX at aol.com> wrote:

> From: DunbarX at aol.com <DunbarX at aol.com>
> Subject: Re: Dispatch-Sending keyDown
> To: use-revolution at lists.runrev.com
> Date: Monday, October 26, 2009, 11:52 AM
> Brian.
> 
> Fair enough. But then we should insist that "dispatch" not
> be allowed to 
> "send" system messages. And now this really is getting to
> be too much.
> 
> I love Rev for the same reasons I love HC. They are
> magnificent 
> intellectual tools manipulatable by mere mortals. Therefore
> I will cut either any break 
> they need; I just want to know how they work.
> 
> Craig Newman
> 
> 
> In a message dated 10/26/09 2:44:11 PM, briany at qldlearning.com
> writes:
> 
> 
> > 
> > Ideally (in my mind), if Rev wants to be strict then
> it should just 
> > not allow you to "send" system messages. Either pass
> them, don't pass 
> > them, or use send with a non-reserved name. Then there
> would be little 
> > room for expecting them to continue to behave as
> system messages.
> > 
> 
> _______________________________________________
> 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
>