Separate user error messages from developer error messages.
An error in the GUI should never display a nonsensical stack trace to the user. All stack traces involving the GUI and other errors made to be read by the developer should be logged to file (and optionally standard out).
#2 Updated by Chad Berkley over 11 years ago
Need to check all error messages to make sure they make sense and that an appropriate message is actually displayed. Many errors just return a dialog that says "null" (see attachment 1).
Many error message are too long for the dialog box and the layout gets cut off. Error messages should resize the dialog so that they message fits. (See attachment 2).
#4 Updated by Christopher Brooks over 11 years ago
The way to fix this bug is that each time a nonsensical error message
appears, then we need to know what the stack trace is and how to
reproduce the bug.
For the "A ridiculous error message" at
we would need to know how to reproduce it and what the stack trace is.
For "error dialog that is cut off" at
This could be associated with "Error message with selectable text"
I would need to know how to reproduce this dialog.