On Aug 21, 2014, at 10:24 PM, Daryle Walker <dary...@mac.com> wrote: > > I changed my app from implementing -application:openFile: to > -application:openFiles: in my application delegate. Then, I noticed that my > Open File menu command directly calls my window creation function, and I > decided to change the action handler to call -application:openFiles: instead. > Later I realized that changing a global via -replyToOpenOrPrint: to the > application object may not be a good idea if said object doesn’t expect it > (like outside of application launch). So now I want to re-reimplement the > open-file action handler by calling the open-file Apple Event to myself.
This is a very strange idea. Cocoa applications do not do this; they just call straight into NSDocumentController. --Kyle Sluder _______________________________________________ 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
