#259 Error reporting is handled inconsistently
I've just noticed that we're not always consistent in the way we're communicating errors. The ErrorLogger framework is setup to write messages out to a file and then later(hopefully soon) prompt the user to check the file.
This isn't being used in situations where we're using the EDT to present a progressbar. If we use DisplayException instead of the ErrorLogger, we're able to cut back through to the SwingWorker and terminate early. What is currently happening in many situations is that we are both posting some detailed message to the ErrorLogger AND passing a simpler message for the user to see through the DisplayException framework. The only problem is that ErrorLogger has its own ideas as to how to alert the user to recent problems. What happens then is that the user immediately sees the message from the DisplayException and at some varying time later sees another error message.
For now, I'm just going to add another ErrorLogger function that just records and doesn't prompt, but there might be a better way to do it.
Logged In: YES
user_id=1535862
Originator: YES
I did that. So now things are a bit cleaner, but it could still be worth thinking about at some point.