[DUG] exception handling

[Alister Christie]

You could probably just put an event on Application.OnException or put 
an event on an TApplicationEvents.OnException.  But it might not handle 
bad things before Application.Initialize or after Application.Run.

But you are probably best off with something more robust as Paul suggests.

Alister Christie
Computers for People
Ph: 04 471 1849 Fax: 04 471 1266
http://www.salespartner.co.nz
Follow us on Twitter http://twitter.com/salespartner
PO Box 13085
Johnsonville
Wellington


On 24/04/2012 3:58 p.m., Ross Levis wrote:
>
> This is likely a simple question but I've never dealt with it before.
>
> Way back in Windows 98 days if an exception was raised, the 
> description of the exception was displayed in a message box.  These 
> days in XP, Vista, 7, you get options to send reports to Microsoft or 
> other obscure dialogs which don't even mention anywhere what exception 
> occurred, even if you click  the "More information" link.
>
> Is there a simple way to get all exceptions to display a message box 
> again before terminating?  It would make life so much simpler when 
> debugging with users.
>
> Cheers,
> Ross.
>
>
>
> _______________________________________________
> NZ Borland Developers Group - Delphi mailing list
> Post: delphi at listserver.123.net.nz
> Admin: http://delphi.org.nz/mailman/listinfo/delphi
> Unsubscribe: send an email to delphi-request at listserver.123.net.nz with Subject: unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://listserver.123.net.nz/pipermail/delphi/attachments/20120424/2baa8483/attachment.html