#13352 closed enhancement (fixed)
[Patch] Adding a new bug report queue.
Reported by: | michael2402 | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | 16.08 |
Component: | Core bugreport | Version: | |
Keywords: | gsoc-core | Cc: | Don-vip, bastiK, stoecker |
Description
Add a new queue that handles bug report dialog display.
We do not need MapView
to check for an active exception handling dialog. If the exception happens again, it will be added to the queue. A good guess is done to allow the user to suppress duplicate messages, so the user is still able to save if e.g. rendering fails.
Attachments (2)
Change History (8)
Changed 7 years ago by
Attachment: | patch-bugreport-queue.patch added |
---|
comment:1 Changed 7 years ago by
Owner: | changed from team to michael2402 |
---|---|
Status: | new → needinfo |
Changed 7 years ago by
Attachment: | patch-fix-13352.patch added |
---|
comment:2 Changed 7 years ago by
Owner: | changed from michael2402 to team |
---|---|
Status: | needinfo → new |
comment:3 Changed 7 years ago by
try { e.printStackTrace(); } catch (RuntimeException e2) { // we cannot do anything more... // re-throwing this causes an infinite loop. }
Isn't it a bit overkill? Did you really find a case where printStackTrace
throws an exception?
comment:4 Changed 7 years ago by
I wanted to overwrite it in ReportedException to only print the real, original stack trace. printStackTrace
also calls getMessage()
which may be implemented by an user to e.g. format the message.
But yes, it is very unlikely to happen ;-).
does not apply cleanly