On Mar 1, 2013, at 16:21:35, Quincey Morris <quinceymor...@rivergatesoftware.com> wrote:
> I think the diversion into Apple Events is something of a red herring, at > least at this stage of your debugging. Requests to open and print may indeed > arrive at your app as Apple Events, but the best place to intervene is in > NSApplicationDelegate protocol. By default, all such external requests should > end up at one or other of the delegate protocol methods. > > If they don't get there, it seems likely the Finder isn't sending them. That > wouldn't solve your problem, of course, but it would tell you that looking in > your app's code isn't going to get to the solution. Sorry, I still consider myself a newbie in Cocoaland. I can add those open and print overrides to my NSApplicationDelegate, but I only want to be able to set breakpoints on them but still let the default behavior happen. Since NSApplicationDelegate doesn't actually implement those methods, I can't simply call [super application:sender openFiles:filenames]; to get that default behavior. So what do I do? I need everything to work at least once in the normal way so I can then see which methods might not be getting called when things start going wrong. -- Steve Mills office: 952-818-3871 home: 952-401-6255 cell: 612-803-6157 _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
