Re: Quitting applications on InstallationCheck
site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com On 19 Jul 2007, at 5:51 PM, Bill Coderre wrote: Thank you, Bill, for the background and help. Am I going astray here? — F _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.a... Apple's policy (which is not followed 100%) is to put up an error immediately if the target app is running. To do this, check for the app running in your InstallationCheck script (or similar part of the distribution script), and just return an error. This means that the user has to switch to the other app, save and close, quit the installer, and then re-run the installer. That's a bit lame... As an experiment, I've tried including, as InstallationCheck, a Foundation/CF/Carbon tool that, if it finds the target application running, posts a CFUserNotification alert asking the user to quit the target and press Continue, or to press Cancel to abandon the installation. I get the "This package contains a program..." alert, but probably it can't be helped, and it's a policy issue as to whether we can live with it. What does my tool return, if the user presses Cancel? I tried 3, and found that the installation continued unimpeded. I tried 96 + 3 = 99, and Installer.app crashed, I assume because it couldn't find a matching message string, and didn't check to see if the message was NULL. This email sent to site_archiver@lists.apple.com
participants (1)
-
Fritz Anderson