• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: keyDown event processing -- harder than it looks?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: keyDown event processing -- harder than it looks?


  • Subject: Re: keyDown event processing -- harder than it looks?
  • From: Michael Crawford <email@hidden>
  • Date: Sun, 16 Jan 2011 20:52:00 -0500

Solved.

I have an NSTableView, which is intercepting keystrokes in order to support type-select functionality.  The solution, in my case was to add the NSTableView delegate method:

– tableView:shouldTypeSelectForEvent:withCurrentSearchString:

And put the keyboard handling code I need in that method.

-Michael

On Jan 11, 2011, at 6:08 PM, Corbin Dunn wrote:

>
> On Jan 11, 2011, at 1:31 PM, Michael Crawford wrote:
>
>> Documentation says NSWindowController inherits from NSResponder.
>>
>> Besides, I was getting the events.  I just don't understand what this message is and why it is being tossed out every 7 keyDown messages.
>>
>> http://developer.apple.com/library/mac/#documentation/cocoa/Reference/ApplicationKit/Classes/NSWindowController_Class/Reference/Reference.html
>>
>
>
> You probably have a view in the responder chain that isn't calling super. Therefore, you have to subclass higher in the responder chain (maybe the view).
>
> corbin
>
>
>
>> -Michael
>>
>> On Jan 11, 2011, at 4:25 PM, Seth Willits wrote:
>>
>>> On Jan 11, 2011, at 11:17 AM, Michael Crawford wrote:
>>>
>>>> I'm trying to process a simple keyDown event by overriding -keyDown on the NSWindowController derived class for my main window.
>>>
>>> The NSWindowController doesn't receive events, only views do.
>>>
>>>
>>> --
>>> Seth Willits
>>>
>>>
>>>
>>> _______________________________________________
>>>
>>> Cocoa-dev mailing list (email@hidden)
>>>
>>> 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:
>>>
>>> This email sent to email@hidden
>>
>> _______________________________________________
>>
>> Cocoa-dev mailing list (email@hidden)
>>
>> 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:
>>
>> This email sent to email@hidden
>

_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:

This email sent to email@hidden

References: 
 >keyDown event processing -- harder than it looks? (From: Michael Crawford <email@hidden>)
 >Re: keyDown event processing -- harder than it looks? (From: Seth Willits <email@hidden>)
 >Re: keyDown event processing -- harder than it looks? (From: Michael Crawford <email@hidden>)
 >Re: keyDown event processing -- harder than it looks? (From: Corbin Dunn <email@hidden>)

  • Prev by Date: Re: Get iphoto scripting bridge handle without starting iphoto?
  • Next by Date: Printing Appears Very Small in Lower-Left Corner of Page
  • Previous by thread: Re: keyDown event processing -- harder than it looks?
  • Next by thread: Responding to changes in outline view
  • Index(es):
    • Date
    • Thread