The point of App.UnhandledException is to supply a hook for replacing the standard "The application will now quit" dialog with one of your own. This is last-chance error-handling. What you should do is to document the methods in your RSS class that raise exceptions. Then, forearmed with this knowledge, users can plan to handle RSSExceptions where they occur.
Charles Yeomans On Apr 25, 2007, at 11:05 AM, Thom McGrath wrote: > I think it may be, as I've just discovered that we can now catch all > exceptions in the App.UnhandledException event. This wasn't the case > a while ago, so I gave up on it. > > But I return true to handle the event (in the demo app), but it still > quits automatically. Is this correct? I thought returning true > suppresses this behavior, at least according to the docs. > > -- > Thom McGrath, <http://www.thezaz.com/> > "You realize you've created God in your own image when God hates all > the same people you do." > > > On Apr 25, 2007, at 10:47 AM, [EMAIL PROTECTED] wrote: > >> Why not? That seems like the right approach to me. _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
