On Mar 4, 2014, at 16:16:53, Kyle Sluder wrote:
> That doesn't seem right… if I press a dead key (like Option-e), then the
> next unmodified space should insert an acute accent in whatever field
> editor is first responder. If your code is triggered solely by virtual
> key code, the user will be
On Tue, Mar 4, 2014, at 12:18 PM, Mills, Steve wrote:
> On Mar 4, 2014, at 13:51:31, Eric Schlegel wrote:
>
> > A little architectural background first: normally, when a keyboard event
> > first arrives in the HIToolbox event queue from the window server, the
> > initial contents are just as yo
On Mar 4, 2014, at 13:51:31, Eric Schlegel wrote:
> A little architectural background first: normally, when a keyboard event
> first arrives in the HIToolbox event queue from the window server, the
> initial contents are just as you saw - a keycode and key modifiers, but no
> unicode values. T
On Mar 4, 2014, at 11:28 AM, Mills, Steve wrote:
> On Mar 4, 2014, at 13:03:34, Mills, Steve wrote:
>
>> I'm seeing something really odd. We get the NSEvent for the current keyDown
>> when the user types an unmodified space. From that we get the eventRef to
>> pass to some legacy code. Somet
On Mar 4, 2014, at 13:03:34, Mills, Steve wrote:
> I'm seeing something really odd. We get the NSEvent for the current keyDown
> when the user types an unmodified space. From that we get the eventRef to
> pass to some legacy code. Sometimes that EventRef will contain the correct
> space charac
