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

Bug 380864

Summary: [Compatibility] IWorkbenchWindowConfigurer's coolbar-visibility property ignored
Product: [Eclipse Project] Platform Reporter: Meng Xin Zhu <kane.zhu>
Component: UIAssignee: Platform UI Triaged <platform-ui-triaged>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: bsd, eclipse, kane.mx
Version: 4.2   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:
Bug Depends on:    
Bug Blocks: 378835    
Attachments:
Description Flags
No coolbar is shown via disabling it in workbench window advisor
none
coolbar is shown even if it's disable none

Description Meng Xin Zhu CLA 2012-05-29 04:39:10 EDT
Eclipse SDK

Version: 4.2.0
Build id: I20120524-2100

1. create a RCP application from template
2. disable showing its coolbar in Workbench window advisor

configurer.setShowCoolBar(false);

3. launch the same application in Juno using 4.2 as target platform

You will see the coolbar of RCP.
Comment 1 Meng Xin Zhu CLA 2012-05-29 04:40:57 EDT
Created attachment 216383 [details]
No coolbar is shown via disabling it in workbench window advisor
Comment 2 Meng Xin Zhu CLA 2012-05-29 04:43:14 EDT
Created attachment 216384 [details]
coolbar is shown even if it's disable

Running the same application in Juno
Comment 3 Brian de Alwis CLA 2012-05-29 10:39:24 EDT
There's a disconnect between the configurer and the window's coolbar and perspective bar, discovered too late for 4.2.

One possible workaround is to disable the top-trim, used to host the coolbar and perspective switcher, using something like the following in your window advisor:

   public void postWindowOpen() {
      WorkbenchWindow win = (WorkbenchWindow) getWindowConfigurer().getWindow();
      win.getTopTrim().setToBeRendered(false);
   }

You'll need to include the org.eclipse.e4.ui.model.workbench bundle.
Comment 4 Brian de Alwis CLA 2012-08-07 10:34:32 EDT

*** This bug has been marked as a duplicate of bug 378835 ***