Community
Participate
Working Groups
Build Identifier: 20100617-1415 I want to have a custom perspective with different tools on the toolbar than the default perspective. When I switch between the perspectives, the tools do not reset unless I explicitly reset the perspective. Reproducible: Always Steps to Reproduce: 1. Open the Java perspective 2. Right-click on the perspective icon and go to Customize... 3. Under Tool Bar Visibility, uncheck the Launch tool bar group and click OK 4. Right-click on the perspective icon and select Save As... 5. Save the perspective as "Launchless Java" 6. Go back to the Java perspective Notice that the Launch toolbar group is not visible even though it should be in the Java perspective. 7. Reset the Java perspective Notice that the toolbar group reappears 8. Switch back to the "Launchless Java" perspective Notice the toolbar group is still visible, even though it shouldn't be in this perspective. 9. Reset the "Launchless Java" perspective Notice the toolbar group disappears again
This is likely some sort of id/caching clash. If you open the Debug perspective then as long as you switch to it before selecting either of the two Java perspectives everything seems to work ok....
(In reply to comment #0) > Steps to Reproduce: > 1. Open the Java perspective > 2. Right-click on the perspective icon and go to Customize... > 3. Under Tool Bar Visibility, uncheck the Launch tool bar group and click OK > 4. Right-click on the perspective icon and select Save As... > 5. Save the perspective as "Launchless Java" > 6. Go back to the Java perspective > Notice that the Launch toolbar group is not visible even though it should be in > the Java perspective. This is correct behaviour. You are changing the Java Perspective (saving another perspective will copy the java perspective info to the new perspective). But yes, switching from the reset java perspective to the new perspective should make the toolbar disappear. PW
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.
