Bug 235203 - [Perspectives] [RCP] Perspective bar, Dock on Top Right does not work when coolbar is invisible
Summary: [Perspectives] [RCP] Perspective bar, Dock on Top Right does not work when co...
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 major with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-02 14:57 EDT by Urszula Krukar CLA
Modified: 2019-09-06 15:32 EDT (History)
2 users (show)

See Also:


Attachments
Bar on the left. (372.99 KB, image/bmp)
2008-06-02 14:57 EDT, Urszula Krukar CLA
no flags Details
Screenshot. (11.11 KB, image/gif)
2008-06-03 15:40 EDT, Urszula Krukar CLA
no flags Details
Screenshot of the perspective bar on the right (to big). (11.06 KB, image/gif)
2008-06-03 15:42 EDT, Urszula Krukar CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Urszula Krukar CLA 2008-06-02 14:57:20 EDT
Created attachment 103178 [details]
Bar on the left.

Steps To Reproduce:
1. Create new Plug-in project (target: Eclipse 3.3, RCP app, RCP application with a view template)

2. Edit ApplicationWorkbenchWindowAdvisor.java

3. Add following line to preWindowOpen() method:
   configurer.setShowPerspectiveBar(true);

4. Run the application and choose 'Dock on -> Top Right' => nothing changes, the bar stays where it was

5. Choose 'Dock on -> Left' => big empty space is left below the main menu.
Comment 1 Eric Moffatt CLA 2008-06-03 15:20:26 EDT
I've just tried this using 3.3.2 and find a slightly different result;

I can successfully switch between 'left' and 'top left' and 'top right' but some of the strange layout behavior does manifest. There are two things you can try in order to mitigate these.

I'm also pretty sure that the large blank area you're seeing is the result of there being no actual tools contributed to the Toolbar (actually the CoolBar). SWT has a nasty habit of returning an arbitrary value of 64, 64 as the default value for 'computeSize'. What happens if you add a tool contribution?

Comment 2 Urszula Krukar CLA 2008-06-03 15:38:20 EDT
This screenshot was made, when coolbar visibility was set to false by
configurer.setShowCoolBar(false);
I don't have a need for coolbar in my app, I want it to be invisible.

I set coolbar visibility to true, I attach screenshots with results.
Comment 3 Urszula Krukar CLA 2008-06-03 15:40:02 EDT
Created attachment 103409 [details]
Screenshot.

Coolbar is visible, perspective bar is located on Top Left.
Comment 4 Urszula Krukar CLA 2008-06-03 15:42:51 EDT
Created attachment 103410 [details]
Screenshot of the perspective bar on the right (to big).

Coolbar visible, perspective bar located on Top Right.

This result is more-less what I want, but I want perspective bar not to be so tall.
Comment 5 Urszula Krukar CLA 2008-06-03 15:48:35 EDT
I just noticed, that I have given you wrong version number - all the screenshots were taken, where target platform version was 3.4.

Build number: I20080516-1333
Comment 6 Urszula Krukar CLA 2008-06-07 04:58:13 EDT
Further investigation results:

Coolbar invisible -> Perspective Bar does not move to the right at all

Coolbar visible but empty -> Perspective Bar moves to the right, but is much too big (probably tdue to 64x64 default size, as you mentioned)

Coolbar visible and an action on it -> Perspective bar works correctly

I think that methods setShowXXX should be independent from one another. One method cannot work only if there is an expected combination of values in other methods.
Comment 7 Eclipse Webmaster CLA 2019-09-06 15:32:52 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.