Bug 83820 - [ErrorHandling] Replace all single "OK" button informational modal requester with something less obnoxious
Summary: [ErrorHandling] Replace all single "OK" button informational modal requester ...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: All All
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-27 07:32 EST by Oyvind Harboe CLA
Modified: 2019-09-06 16:15 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Oyvind Harboe CLA 2005-01-27 07:32:03 EST
Eclipse puts up modal requesters with some information and a single "OK" button.

E.g. "Could not contact the CVS server" [OK].

It is very annoying to have focus stolen from the editor I'm currently working
in. Even more annoying if I click the wrong spot and accidentally send the modal
dialog box to back. (Can happen w/GTK + Xming X server).

Perhaps something akin to the "MSN Messenger" non-focus-stealing, non-modal
notifications that something is amiss, with a possiblity to go and examine the
modal dialog box queue at a later time.

Incidentally it would be nice to be able to copy&paste the text in the error
message, which I'm not sure you can directly from the modal dialog box.

Øyvind
Comment 1 Susan McCourt CLA 2009-07-09 15:51:10 EDT
This bug is quite old, but I think still relevant.
I'm not even sure if the specific case (CVS) is still true, but in the current code stream, I interpret this request to mean something like:

"the status handler should do something less obstrusive when the style is StatusManager.SHOW"

We get similar complaints in p2 about "server not found" errors.  
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:15:25 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.