Re: didPrint selector not called
Re: didPrint selector not called
- Subject: Re: didPrint selector not called
- From: Jeremy Hughes <email@hidden>
- Date: Fri, 16 Dec 2016 19:33:42 +0000
> On 16 Dec 2016, at 19:29, John McCall <email@hidden> wrote:
>
>> On Dec 16, 2016, at 11:24 AM, Jeremy Hughes <email@hidden> wrote:
>> Thanks for the link.
>>
>> I’ve looked at it, and I don’t think it applies in this case, because I’m not actually overriding the document(_:didPrint:contextInfo:) method, just providing it as a callback. There isn’t an override keyword before the method, and there isn’t a superclass method that I can call through to. I suppose it would apply if I had a subclass (of my document class) that needed to override the callback. Does that seem right to you?
>
> You're overriding printDocumentWithSettings to ignore the passed-in delegate and selector. Unless you're certain that the passed-in delegate and selector are never useful, you're probably breaking something.
>
> John.
OK - I misunderstood what Quincey was saying.
The passed-in delegate and selector are nil, but I obviously can’t be sure that they will always be nil.
All I’m actually trying to do is to clean up some objects that need to exist during the print operation. Is this the best way for me to be doing that?
Jeremy
_______________________________________________
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