Community
Participate
Working Groups
Build Identifier: 20110218-0911 When an editor is in full screen mode and a view gets opened via IWorkbenchPage.showView() and that view gets closed by the user via the X/close icon and opened again the view ^does not get rendered properly. This only happens if the view gets opened inside a view container which is empty. Reproducible: Always Steps to Reproduce: 1. Download current Eclipse IDE for Java Developers 2. Create new Java project 3. Create new JUnit test class with one test method 4. Close all views in the perspective other than the editor which holds the test class 5. Bring editor in full screen mode via double-click on the title tab 5. Right-click on the test class and execute "run as->JUnit Test" 6. JUnit pops up, display result -> close view via the X button on the title tab 7. Execute tests again via "run as->JUnit Test" 8. View appears again but is not rendered properly (just one gray surface)
Created attachment 192844 [details] Shows how the rendering bug looks like
I can't reproduce this one. Is there anything in your Error Log?
Created attachment 193174 [details] Screencast showing the rendering problem Please find attached a screencast showing the problem. I hope that the issue is now reproducable.
Possibly a windows specific bug. Remy can you reproduce this?
I can reproduce using N20110413-2000 and 3.6.2 on Windows XP: 1. start with new workspace 2. paste this into the Package Explorer: public class a extends TestCase { public void testIt() { } } 3. use quick fix to add JUnit 3 libraray 4. close the Outline view 5. editor context menu > Run As > JUnit Test 6. move the JUnit view to the right side of the editor (where Outline was) 7. close the JUnit view 8. maximize the editor (double-click o its tab) 9. editor context menu > Run As > JUnit Test 10. close the JUnit view by clicking on the tab's 'X' 11. editor context menu > Run As > JUnit Test ==> view not rendered correctly I assume this is not platform specific.
Dani, what happens if you re-open the view manually (Ctrl-3 or explicit 'Show View' rather than having it open auto-magically as a result of running the JUnit ? Also, does your comment indicate that you don't actually have to close all the views to get into this state (just that we auto-open a closed view in a minimized stack with no other views) ? Does the view appear if you click on the stack ? From the initial description I wasn't inclined to tackle this in 3.7 because the conditions seemed unlikely to be hit under normal workflows (i.e. the workaround is to not close the JUnit view).
(In reply to comment #6) Eric, are you saying you cannot reproduce using my steps from comment 5? I just tried them again on I20110428-0848 and they easily reproduce the problem, at least on Windows XP. > Dani, what happens if you re-open the view manually (Ctrl-3 or explicit 'Show > View' rather than having it open auto-magically as a result of running the > JUnit ? If I explicitly open the view in step 11 (instead of running the tests) then the view shows correctly. > Also, does your comment indicate that you don't actually have to close all the > views to get into this state Yes, Package Explorer and all other views are open when I maximize the editor. >(just that we auto-open a closed view in a > minimized stack with no other views) ? I don't see an empty minimized stack after step 10. > Does the view appear if you click on the stack ? Yes.
Just a short info. This problem is also reproducable on Ubuntu 10.10 with Eclipse Version: 3.6.2 Build id: M20110210-1200 by doing the steps described in comment 5. With best regards, Tobias
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. If the bug is still relevant, please remove the "stalebug" whiteboard tag.
