Re: UI changes in reporting of exceptions

Jaroslav Tulach wrote:
>> - provide a way to not show this dialog again
> 
> Do we really need it or want it? I do not think so. Jesse mentioned
> that he wants it, but imho it is not desirable to supres the dialog.
> We want bug reports and ignoring bugs in dev builds should not be
> easy.

1. The user decides whether or not he or she wants to report bugs. Not 
you or anyone else.

2. Wishing to avoid the dialog is not the same as ignoring bugs. I 
always suppress this dialog and I file tons of bugs with stack traces. 
The flashing error icon is a significant visual indication that an 
exception has been caught; after seeing that, you have the choice of 
opening the dialog on your own time, after finishing whatever you were 
doing, or looking in the log file / console.

3. There are some circumstances where the dialog can cause data loss. If 
a bug causes an exception to be thrown over and over, you can never get 
the dialog to stay closed. I have also seen bugs which are thrown by 
code in the AWT paint loop - so the bug is thrown once, you see the 
dialog, close the dialog, and the resulting exposure event causes it to 
be thrown again. In such cases it may not be possible to get the IDE 
back into a usable state and it must be killed externally - which can 
cause unsaved edits to be lost, unless you know how to log into the IDE 
with a script console and manually invoke LifecycleManager.saveAll.

-J.

-- 
[email protected]  x22801  netbeans.org  ant.apache.org
       http://google.com/search?q=e%5E%28pi*i%29%2B1