On Mar 1, 2013, at 13:59 , Steve Mills <smi...@makemusic.com> wrote:

> I have tons of experience with AppleEvents under Carbon, but none under 
> Cocoa. Where does that event come in?

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.


_______________________________________________

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

Reply via email to