[Metacard] RE: capturing the "return" key in a field
John Vokey
vokey at uleth.ca
Mon Nov 26 17:40:01 EST 2001
Never mind. Re-starting metacard solved the problem, although I have no
idea how that could possibly help.
--
It has become almost a cliché to remark that nobody boasts of ignorance of
literature, but it is socially acceptable to boast ignorance of science.
-- Richard Dawkins
John R. Vokey, Ph.D.
Professor
Department of Psychology and Neuroscience
University of Lethbridge
----------
> From: John Vokey <vokey at uleth.ca>
> Date: Mon, 26 Nov 2001 15:04:11 -0700
> To: <metacard at lists.runrev.com>
> Subject: capturing the "return" key in a field
>
> Ok, I give up. What's the secret? This should be obvious and simple, but I
> can't get any of the alternatives to work. I have a simple field that
> collects responses when given the focus, and I want to prevent the user from
> typing a return into the field. However, none of keyDown, rawKeyDown, etc.
> seem to do it. In the ref stack, it is implied for all that all I have to do
> is *not* pass the key if it is return and all should be fine, but regardless
> of what I do ***even if I pass nothing from the handler*** a return is still
> entered into the field. What gives? For example, the handler in the field
> scipt:
>
> on rawKeyDown x
> end rawKeyDown
>
> *still* puts a return in the field! I am more than a little baffled, not to
> say frustrated. Metacard PPC 2.4.
> --
> "Life results from the non-random survival of randomly varying replicators."
> -- Richard Dawkins
>
> John R. Vokey
More information about the metacard
mailing list