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. Looking through the modern Apple docs, I see all sorts of stuff about handling Apple Events, but nothing about sending them. Help.
(The app doesn’t use the NSDocument architecture. In fact, I ripped that out.) Oh, is there a non-retired list of the basic Apple Events and their required and optional parameters? (If some Apple expert says calling [NSApp replyToOpenOrPrint:X] arbitrarily is OK, I still want to switch to Apple Events.) — Daryle Walker Mac, Internet, and Video Game Junkie darylew AT mac DOT com _______________________________________________ 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
