On 6/6/12 2:34 PM, koko wrote: > On Jun 6, 2012, at 3:25 PM, Erik Stainsby wrote: > >> I think the approach you would use is to employ -[NSWorkspace] to launch the >> other app on your behalf. > > I was looking at that. Not sure how to determine if the app was launched that > way and not by a user. > > Any suggestions?
Use –[NSWorkspace launchApplicationAtURL:options:configuration:error:] and set the configuration dictionary contents to something meaningful to the app being launched. You could probably also rig something up by registering your app to act as a custom protocol handler, then pass information in via the URI. This might be more useful if you want third-party apps to be able to easily open your app with certain options, but is likely a little messier than just launching with configuration options. Would you care to explain what your motivation is? We might also be able to suggest an alternate approach entirely that would better suit your needs. -- Conrad Shultz Synthetiq Solutions www.synthetiqsolutions.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
