On Sat, 22 Sep 2012 00:38:36 -0500, Ken Thomases said: >I have no inside knowledge, but I think you've misunderstood the purpose >of this default.
I guess I have. Thanks Ken & Corbin for straightening me out. :) >If you want to change how uncaught exceptions are handled more >generally, you should look into Exception Programming Topics: >Controlling a Program’s Response to Exceptions <https:// >developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/ >Exceptions/Tasks/ControllingAppResponse.html> and NSExceptionHandler. >Of course, you should first strive to make sure your app doesn't raise >exceptions, but no amount of programming care or testing can guarantee >that it can never happen in the field. Yes, I agree with and am aware of all that. I currently use FeedbackReporter: <https://github.com/tcurdt/feedbackreporter> to handle the (mostly rare) exceptions that make it to the user. I was thinking that NSApplicationShowExceptions was maybe meant to replace such things. FeebackReporter works mostly well but I'm unsure of the correct way to handle uncaught exceptions on non-main threads/queues. It seems to always result in the app being killed no matter what I do. Cheers, -- ____________________________________________________________ Sean McBride, B. Eng s...@rogue-research.com Rogue Research www.rogue-research.com Mac Software Developer Montréal, Québec, Canada _______________________________________________ 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
