> In order for your custom view to become first responder, it must also return
> YES from -acceptsFirstResponder
head ... desk
Off course! I bet that was it ...but as you said: to avoid surprises I
better move the action off the first responder.
Thanks, Graham!
cheers,
Torten
> but mouse event
I now have changed the actions in the menu to go through my controller
which (at least in this case) is just fine. Now I can start and
configure the NSPrintOperation myself.
But I am still wondering what was wrong with going through the first responder.
cheers,
Torsten
On Tue, Oct 4, 2011 at 12:
On 04/10/2011, at 9:23 PM, Torsten Curdt wrote:
> "Printing is generally initiated by the user choosing the Print menu
> command, which usually sends either a print: or printDocument:
> message,
So which is it? You can look at the Print menu item in the MainMenu.xib and see
what its action and
I have a non-document based app. It's a master detail layout with a
NSOutlineView and a custom NSView (in a NSScrollView in a NSSplitView)
on the right. Now when I initiate a "Print" from the menu all that
shows up in the print preview is the outline view.
Reading the documentation from
http://dev