On Jul 28, 2005, at 3:35 AM, Florian Dejako wrote:
Dear Carbon-Dev,
My WaitNextEvent-based application has compositing windows with
standard window handlers. The problem I have is with the
propagation of kEventTextInputUnicodeForKeyEvents.
When none of the views in the windows is focused, everything works:
When I press a key, a kEventTextInputUnicodeForKeyEvent is received
by my WindowEventTarget (which returns eventNotHandledErr), and
then by my ApplicationEventTarget (which also returns
eventNotHandledErr). WaitNextEvent then rewards me with a keyDown
event.
If one of the views in the windows has the keyboard focus, it's
different: kEventTextInputUnicodeForKeyEvents are received by the
focused view, and if that returns eventNotHandledErr, propagate to
the WindowEventTarget. Just like before, this returns
eventNotHandledErr. Things turn sour from here on, as the
ApplicationEventTarget never receives any
kEventTextInputUnicodeForKeyEvent, and WaitNextEvent returns a
nullEvent, followed by a keyUp event.
The behavior is the same in Panther and Tiger, and breaks
application-level keyboard events whenever a view is focused.
Is kEventTextInputUnicodeForKeyEvent not the event I should be
responding to for keyboard events?
What do I need to do to fix the event propagation to the application?
kEventTextInputUnicodeForKeyEvent should be working in this case, I
think. Can you turn on event tracing with TraceEventByName for this
particular event and see what output is generated? That might point
out where the event is being handled, at least.
-eric
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
