Sending keyDown

[J. Landman Gay]

DunbarX at aol.com wrote:
> Jim.
> 
> Thought some more about your post.
> 
> What I am trying to do is get typed chars into the field, and then work on 
> the actual text of that field. 
> 
> That was why the idea of sending keyDown in the handler's first line is so 
> nice; it loads the field, and still leaves the remainder of the handler open 
> for processing. I cannot pass keyDown, the only thing that actually works, 
> because doing so ends the handler.

Seems like it should work if you change the processing to use a keyup 
handler instead. Don't even trap keydown at all. The engine will put the 
character into the field after a keydown all by itself, and when the key 
is released, you do whatever is needed.

I'm not sure why your original method isn't working, but what it looks 
like is that when you send a message to the stack, it just stops there 
and doesn't traverse the hierarchy. If there's no matching handler, you 
get the error.

If you do need to use a keydown for some reason, then you can 
specifically put the character into the field in the first line of the 
handler and then do your work on the text:

on keydown whichKey
  put whichKey into the selection
  -- process here
end keydown

-- 
Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com