Supress the exception dialog was: UI changes in reporting of exceptions
Jaroslav Tulach <[email protected]>
| Newsgroups | gmane.comp.java.netbeans.user-interface |
|---|---|
| Organization | Sun Microsystems |
| Message-ID | <[email protected]> |
I believe this discussion is completely independent from the UI Gesture Collector one (at least with current proposal of having just the "report..." button) and my desire is to not continue it nor solve it. If anyone else wants, go on start your own UI review. <quote who="Jesse Glick"> > 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. I believe that QA guys do not consider such behaviour sufficient enough for dev builds. At least they shout at me whenever there is a chance an exception would not open a dialog. > 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. I've also faced similar situations, however I know that the dialog is not modal and that it is enough to minimize it and ignore it. -jst