On Fri, 10 Dec 1999, Mark Lacy wrote:
> Scott you wrote regarding my numlock key question:
>
> >Another thing to consider would be to just override *all* of the
> >keyDown events and do entry based on the parameter to the rawKeyDown
> >message. That way it wouldn't matter what the state of that key was.
> Could you elaborate on HOW you override *all* of the keyDown
> events. I don't know how you would go about this? I have tried
> KeyDown and RawKeyDown at the card level and field levels without
> passing the message and yet still the state of the numlock key
> changes.
You'd just handle all of the rawKeyDown messages and not pass them.
Build a table where you do your own remapping of the raw key code to a
letter/number and then put the translated value into the selection (to
build the table, write a script that gathers this info and then type
each key on the keyboard, saving it into a custom property array on
some object). Not a lot of fun, but not particularly difficult
either. If it was me, I'd probably just tell the user to make sure
the light was on or off, depending on what you need ;-)
Regards,
Scott
> Hoping,
>
> Mark Lacy
> LetterPress Software, Inc.
********************************************************
Scott Raney [EMAIL PROTECTED] http://www.metacard.com
MetaCard: You know, there's an easier way to do that...
