Re: Best way to catch signals in a Cocoa app (Or should you?)
Re: Best way to catch signals in a Cocoa app (Or should you?)
- Subject: Re: Best way to catch signals in a Cocoa app (Or should you?)
- From: John Clayton <email@hidden>
- Date: Mon, 15 Nov 2004 18:46:52 -0500
Hi,
Thought I'd try this one more time. Any takers?
J
On Nov 14, 2004, at 5:48 PM, John Clayton wrote:
Hi,
Let's say you need to do some cleanup (like terminating some spawned
tasks) no matter how your app is quit. So even if someone kills the
process from a terminal, the cleanup still happens. I assume using
signal handlers are the only way to get access to these events
(because handling uncaught exceptions didn't seem to work), but how
does one integrate these into a Cocoa app, i.e. where is the proper
place to implement them, and what is the correct procedure for getting
some object methods called (I know from this list that you can't call
ObjC code directly from a signal handler). Any help is appreciated.
Thanks,
John
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden