Bug 128296

Summary:	[RCP] If one perspective has a cool bar, others that don't are affected by it.
Product:	[Eclipse Project] Platform	Reporter:	Christopher Goy <goyenator>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	ASSIGNED ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	ian.leslie
Version:	3.1.1	Keywords:	helpwanted
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Christopher Goy

2006-02-16 15:52:07 EST

I am working on an application which one perspective has a coolbar and all other ones have no coolbar.  When the application is in any perspective except the one with the coolbar there is a gap between the menubar and the rest of the application.  This bug can be reproduced by creating an arbitrary perspective with a coolbar that has at least one button on it, and another perspective that has no coolbar.  The gap can be seen best when the 'perspective bar' is layed out horizontally across the entire application. 
This was done with Eclipse SDK Version: 3.1.1 Build id: M20050929-0840

Comment 1 Christopher Goy

2006-02-16 15:53:44 EST

*** Bug 128294 has been marked as a duplicate of this bug. ***

Comment 2 Nick Edgar

2006-02-20 10:06:00 EST

Agreed that this is a bug.  The coolbar should hide itself when it has no contributions.  The workaround is to ensure that it always has some content, e.g. add a CoolBarContributionItem in the ActionBarAdvisor's fillCoolBar method, or via an action set with visible="true" (although that can be hidden by the user if you include the perspective customization dialog).

Comment 3 Nick Edgar

2006-03-15 11:24:36 EST

Reassigning bugs in component areas that are changing ownership.

Comment 4 Boris Bokowski

2009-11-26 16:15:21 EST

Prakash is now responsible for watching bugs in the [RCP] component area.

Comment 5 Eclipse Webmaster

2019-09-06 16:18:36 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.