Originally reported by: Marcel Bollmann (Bitbucket: mbollmann, GitHub: mbollmann)
Exceptions in the GUI shouldn't usually occur, hence the name "exception".
However, if anything does go wrong, the GUI just hangs. This is bad[tm] -- if this happens during a loading screen, the user is under the assumption that the loading still continues; if this happens at some other time, some parts of the GUI (or maybe everything) just stop working without any indication why.
At a bare minimum, CorA should:
Signal that an exception has happened
Try to save any unsaved changes if a document is currently opened
Originally reported by: Marcel Bollmann (Bitbucket: mbollmann, GitHub: mbollmann)
Exceptions in the GUI shouldn't usually occur, hence the name "exception".
However, if anything does go wrong, the GUI just hangs. This is bad[tm] -- if this happens during a loading screen, the user is under the assumption that the loading still continues; if this happens at some other time, some parts of the GUI (or maybe everything) just stop working without any indication why.
At a bare minimum, CorA should:
Some resources: