Weird. Examining the firstResponder shows it is, in fact, my SCNView subclass.
Yet menu actions to the first responder don't propagate up.
> On Jul 4, 2018, at 21:31 , Ken Thomases wrote:
>
> On Jul 4, 2018, at 10:45 PM, Rick Mann wrote:
>>
>> I've overridden -acceptsFirstResponder to return
> On Jul 4, 2018, at 21:31 , Ken Thomases wrote:
>
> On Jul 4, 2018, at 10:45 PM, Rick Mann wrote:
>>
>> I've overridden -acceptsFirstResponder to return true on the window
>> controller and view controllers.
>
> That doesn't do anything. -acceptsFirstResponder is a view method and is
>
> On Jul 4, 2018, at 21:31 , Ken Thomases wrote:
>
> On Jul 4, 2018, at 10:45 PM, Rick Mann wrote:
>>
>> I've overridden -acceptsFirstResponder to return true on the window
>> controller and view controllers.
>
> That doesn't do anything. -acceptsFirstResponder is a view method and is
>
On Jul 4, 2018, at 10:45 PM, Rick Mann wrote:
>
> I've overridden -acceptsFirstResponder to return true on the window
> controller and view controllers.
That doesn't do anything. -acceptsFirstResponder is a view method and is only
called on views, not controllers.
> I don't have any custom
> On Jul 4, 2018, at 20:40 , Ken Thomases wrote:
>
> On Jul 4, 2018, at 9:08 PM, Rick Mann wrote:
>>
>> I'm writing a new macOS app. I started with the document-based app template
>> (no core data). I have a custom window controller, and a hierarchy of custom
>> NSViewControllers embedded
On Jul 4, 2018, at 9:08 PM, Rick Mann wrote:
>
> I'm writing a new macOS app. I started with the document-based app template
> (no core data). I have a custom window controller, and a hierarchy of custom
> NSViewControllers embedded in a split view controller (I even subclassed the
> split
I'm writing a new macOS app. I started with the document-based app template (no
core data). I have a custom window controller, and a hierarchy of custom
NSViewControllers embedded in a split view controller (I even subclassed the
split view controller).
I have a simple IBAction method that
