ErrorDialog should have maximum size to avoid big size when Error Message is...

A trading platform including ERP, CRM, and accounting

Brought to you by: danielmazurek, fleque, grmpf, jfirechief, and 2 others

#12 ErrorDialog should have maximum size to avoid big size when Error Message is quite long

Milestone: HEAD

Status: closed-works-for-me

Owner: Marc Klinger

Labels: None (24)

Priority: 5

Updated: 2010-09-15

Created: 2008-07-07

Creator: jfirechief

Private: No

DO NOT EDIT OR ANSWER THIS ISSUE. SEE THE ORIGINAL ISSUE INSTEAD:
https://www.jfire.org/modules/bugs/view.php?id=580
ORIGINAL REPORTER: daniel

When multiple errors occur the DefaultErrorDialog collects them and shows the error message in the detail textfield which leads to the fact that the error dialog size can get quite big, if the error message is long.
An Maximum size would be good, and further more the text should be wrapped

Discussion

jfirechief - 2008-07-07

labels: --> None

milestone: --> HEAD
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

jfirechief - 2008-07-07

Logged In: YES
user_id=1828570
Originator: YES

ORIGINAL COMMENT BY daniel, VIEW IT HERE:
https://www.jfire.org/modules/bugs/view.php?id=580

This does not happen with our own DefaultErrorDialog but with the Eclipse standard Error dialog, which is used e.g. something went wrong in an Eclipse Job

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

jfirechief - 2008-07-07

Logged In: YES
user_id=1828570
Originator: YES

ORIGINAL COMMENT BY Marc, VIEW IT HERE:
https://www.jfire.org/modules/bugs/view.php?id=580

At least our job implementation should trigger our error handler. What about setting our handler as the job threads throwable handler before starting the job and resetting the old handler afterwards?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

jfirechief - 2008-08-06

Logged In: YES
user_id=1828570
Originator: YES

ORIGINAL COMMENT BY nick, VIEW IT HERE:
https://www.jfire.org/modules/bugs/view.php?id=580

close?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

jfirechief - 2008-08-13

Logged In: YES
user_id=1828570
Originator: YES

ORIGINAL COMMENT BY Marc, VIEW IT HERE:
https://www.jfire.org/modules/bugs/view.php?id=580

yes

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

jfirechief - 2008-08-13

assigned_to: nobody --> tscharly

status: open --> open-works-for-me
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

jfirechief - 2010-09-15

status: open-works-for-me --> closed-works-for-me
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

jfirechief - 2010-09-15

ORIGINAL COMMENT BY daniel, VIEW IT HERE:
https://www.jfire.org/modules/bugs/view.php?id=580

This does not happen with our own DefaultErrorDialog but with the Eclipse standard Error dialog, which is used e.g. something went wrong in an Eclipse Job

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

jfirechief - 2010-09-15

ORIGINAL COMMENT BY Marc, VIEW IT HERE:
https://www.jfire.org/modules/bugs/view.php?id=580

At least our job implementation should trigger our error handler. What about setting our handler as the job threads throwable handler before starting the job and resetting the old handler afterwards?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

jfirechief - 2010-09-15

ORIGINAL COMMENT BY nick, VIEW IT HERE:
https://www.jfire.org/modules/bugs/view.php?id=580

close?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

jfirechief - 2010-09-15

ORIGINAL COMMENT BY Marc, VIEW IT HERE:
https://www.jfire.org/modules/bugs/view.php?id=580

yes

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.