Dispatch-Sending keyDown

[DunbarX at aol.com]

Mark.

A char typed into a field is actually written via a "keyDown" message 
reaching the engine. It doesn't just appear there via some other mechanism. At 
least that is what I believed. How it gets there is a matter of choice. This 
all seems like what I would consider "normal handling".

So I just wanted to know why I could not send that message explicitly, by 
hand. You can in HC, and I wondered why you could not in Rev. Why would it 
not continue along, like all other messages:

on sendBeep
   send "beep" && 3 to this stack
end sendBeep

This works fine. What is the thing about keyDown? In other words, what is 
the difference, trying to understand the way things work. If your point is 
that the message is stopped for some reason if I intercept it and send it 
rather than passing it to the engine, then I am really confused.

I am with Richard in thinking it is some sort of bug.

Craig Newman

In a message dated 10/23/09 4:21:43 PM, mwieder at ahsoftware.net writes:


> But by dispatching the message you're saying "don't handle this char
> here, but instead bypass the normal handling and give the char
> directly to the stack script." If it's not handled there it will get
> passed on to the backscripts, engine, etc. But nothing is going to
> place the char into your field because you've very explicitly stopped
> that from happening.
>