Community
Participate
Working Groups
3.4.x and latest builds. 1. enable the 'Editor Presentation' action set via Window > Customize Perspective... 2. open another file in the Text editor 3. open a file in the Java editor 4. switch between the two ==> icons in the 'Editor Presentation' tool bar are very noisy, positions change and some disappear. The unused icons should be grayed out to reduce the noise and only when the last Java editor is closed it should remove the contributed action set from the tool bar.
"major" is defined as: major loss of function Btw, I could not reproduce this with an M5 build. I believe you are now seeing toolbar management issues that have plagued others for a long time.
>"major" is defined as: major loss of function Of course you are right, it's not a major loss of function but a major pain to the eyes. >Btw, I could not reproduce this with an M5 build. Right, sorry. I should have checked latest builds before. You can no longer see it since M5 because enabling action sets is broken there (see bug 264312). Please try 3.4.1 or 3.5 M3 with these steps (same as comment 0 but more detailed): 1. download Eclipse SDK 3.4.1 (or 3.5 M3) 2. install it 3. start with a new workspace 4. close Welcome page 5. Window > Customize Perspective... 6. click on the 'Commands' tab 7. 'Editor Presentation' should be unchecked - check it now 8. click 'OK' 9. create a new Java project 'P' 10. create a new file 'f' in 'P' ==> file is opened in the Text editor 11. use the New Java Class wizard to create class 'Foo' 12. switch between the two by clicking on the editor tabs ==> you will see that the toolbar icons (see picture) move around
Created attachment 125884 [details] Picture showin area of flickering
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.
