Community
Participate
Working Groups
I20030909 Currently if an error occurs in a background job and want to get rid of the red blinking I have to 1. go to the lower left icon 2. double-click it to open the Progress view 3. clear the error state 4. close the view again (I know I could use fast view). It would be good if - the hover would show the error - I could clear the errors (maybe only the state so that I can look at the errors later?) directly via the icon (e.g. context menu)
There is now an error dialog that collects up errors. Progress View is not required for this anymore.
How do I access the dialog?
Do you mean programmatically or physically? It will pop up on its own whenever a job returns a status with an Error
I meant physically.
OK great. Is there anything you see as a problem with this solution then?
What if there's a job which causes errors all the time? Will I get interrupted by dialogs all the time? With the old solution I had to go via view but at least I was in the loop to decide when to do this.
No - you will get one non modal dialog that just gets added to if new errors arrive. I wanted to prevent the tons o' dialogs issues we have had in the past.
As Dani mentioned in comment 6, you'll have a real problem if a background job repeatedly causes an error. In fact, the UI gets almost completely blocked by the modal error dialog. You can see that when you provoke bug 48502: public class Example { public Example() { } // <- insert '{' before comment public static void main(String[] args) { } } Inserting the brace causes an exception in SelectionListenerWithASTManager, which reopens the error dialog instantly after is has been closed. To avoid blocking the UI, the error dialog must at least be modal and not take the focus. However, I personally would prefer the solution from comment 0.
Oops, I overlooked that the error dialog is already non-modal. But I still think that the dialog should not take focus when it opens. Focus or not, I see an accessibility problem: - Dialog takes focus: How can a blind user get out of the loop by only using the keyboard? I'm not aware of a shortcut to re-activate the editor when the non-modal dialog is shown. - Dialog doesn't take focus: How can the blind user activate the error dialog to see what's in there?
Marku, the diaog is not modal and the other problem is captured in bug 49999. Suggest to close this one again.
Closing, I should have added my comments to bug 49999. Sorry for the confusion.
Verified in 20040210
