On Fri, Apr 30, 2010 at 8:48 AM, Bill Appleton <billapple...@dreamfactory.com> wrote: > hi all, > > this is great, thanks for the help. > > one issue is that the old carbon kEventTextInputUnicodeForKeyEvent delivered > typed characters that should be inserted into (say) of text field > > the new [event characters] method delivers ALL keys -- so for example, an > arrow key gets a unicode equivalent & now that is also getting typed > > does anyone know how to filter between characters that should be typed & > other stuff?
You can look at the modifier flags and/or detect the unicode code space being used. With that said if you are trying to process text input into text fields using NSEvents you really should reconsider if at all possible. You will miss out on the text input capabilities that Cocoa provides to you for free when you use standard AppKit controls or higher level text input constructs. -Shawn _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
