Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 151070

Summary:	[Contributions] SubStatusLineManager.setMessage(String) does not work
Product:	[Eclipse Project] Platform	Reporter:	Denis Jouvin <denis.jouvin>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P5	CC:	remy.suen
Version:	3.2	Keywords:	helpwanted
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Denis Jouvin

2006-07-19 08:18:10 EDT

The setMessage(String) does not work with the IStatusLineManager returned by getActionBars().getStatusLineManager() on an IViewSite.

The implementation is SubStatusLineManager. Looking at the code, line 115, it seems that this method invokes setMessage(String) on the parent StatusLineManager, which slightly differs from the previous method setErrorMessage(String), which works fine but invokes the setErrorMessage(Image, String) on the parent StatusLineManager, passing null as the image.

Strangely, the setMessage(Image, String) works fine, passing null as image.

I looked a bit further in the code but did not find the cause of this bug.

Workaround: use setMessage(null, yourString).


regards,

Denis Jouvin.

Comment 1 Paul Webster

2007-04-05 19:05:19 EDT

Assigning to component owner
PW

Comment 2 Remy Suen

2007-08-29 08:12:58 EDT

Denis, I cannot reproduce this on 3.4M1. Could you try that release or 3.3.0 and let us know if it's still a problem?

Comment 3 Eclipse Webmaster

2019-09-06 15:31:21 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.

Comment 4 Eclipse Webmaster

2019-09-06 15:38:26 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.

Comment 5 Eclipse Genie

2021-10-09 15:49:22 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.