Even if this is the case, if you send a kill signal to a GUI Cocoa
application, that application's app delegate will not receive -
applicationWillTerminate:. If the application has any important
cleanup/shut down code to run, it won't happen.
I'd go with "don't kill GUI apps unless they're malfunctioning" here.
--
m-s
On 28 Aug, 2008, at 13:47, Randall Meadows wrote:
On Aug 28, 2008, at 11:39 AM, Martin Stoufer wrote:
Actually no, since the default kill signal is TERM, apps will be
allowed to prompt to save if necessary. This assumes the app is
handling that signal properly. We could send KILL or ABRT and that
would just end the processes w/o any save options.
Well, then there must be a lot of apps out there that don't handle
it properly. TextEdit, Pages, Word, Omnigraffle all failed to
prompt me to save dirty documents when I used killall on them.
Granted, that's a small data sample, but I'd be right (and rightly)
pissed at anyone that decided that all those other programs were
written wrong, and decided to use killall anyway.
On a Mac system, this is simply NOT the right way to do this.
_______________________________________________
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:
http://lists.apple.com/mailman/options/cocoa-dev/mikey-san
%40bungie.org
This email sent to [EMAIL PROTECTED]
_______________________________________________
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
