Bug 44831

Summary:	[GlobalActions] Request for ability to set transient status messages
Product:	[Eclipse Project] Platform	Reporter:	Eric Estievenart <eric.estievenart>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	ASSIGNED ---	QA Contact:
Severity:	enhancement
Priority:	P5	CC:	georg.rehfeld, remy.suen, yharms
Version:	3.0	Keywords:	helpwanted
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Eric Estievenart

2003-10-14 12:49:56 EDT

e.g in a global action, not associated to any view/editor,
it would be great if we could have a transient status message
displayed in the status bar, with automatic removal
after the delay has expired.

This would avoid the ugly and inelegant kludge described in
http://dev.eclipse.org/newslists/news.eclipse.platform/msg07818.html
(and followups), which may not work if there is no view/editor open,
and really messes the editors/views status bars.

--Steve

Comment 1 Georg Rehfeld

2004-07-13 23:25:58 EDT

I second the request: global actions, especially those meant to be lightweight,
quick and invoked by just a keystroke have often no other means of messaging the
user other than by means of a status line message: dialogs disturb the user and
are overkill.

The fact, that the global action seems to have no way of having it's own status
line (manager) it must abuse currently the status line of the active part,
(whichever just is active) thereby cluttering the message set by the owner.

And there ARE views, that assume, nobody else writes to their status line!

Georg

Comment 2 Chris McLaren

2005-12-12 16:57:36 EST

Reassigning to Platform-UI-Inbox (I left IBM 18 months ago..)

Comment 3 Michael Van Meekeren

2006-04-21 14:05:43 EDT

Moving Dougs bugs

Comment 4 Paul Webster

2007-04-05 19:02:44 EDT

Assigning to component owner
PW

Comment 5 Eclipse Webmaster

2019-09-06 15:30:05 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.