Community
Participate
Working Groups
There is an empty view in my Java Perspective that cannot be closed. It seems to be attached to my main group of views. If I attempt to minimize this empty view it also minimizes all of the other main views I have open. I can create more of the empty views by dragging the current empty view into a new location on the UI. The old empty view persists and a new one is created, also unable to close it. -- Configuration Details -- Product: Eclipse 1.3.2.20110218-0812 (org.eclipse.epp.package.java.product) Installed Features: org.eclipse.jdt 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
Can you try - restarting eclipse - Window > Reset Perspective If it does not help can you please post - a screenshot - complete configuration details from Help > About > Installation details > Configuration details. You may have some additional plugins installed which contribute this view.
Created attachment 207839 [details] Marked Up Screenshot of Empty View
Created attachment 207840 [details] Eclipse Configuration Details
(In reply to comment #3) > Created attachment 207840 [details] > Eclipse Configuration Details So you have ADT (Android dev toolkit) and GWT installed. Maybe one of them caused the problem? (In reply to comment #2) > Created attachment 207839 [details] > Marked Up Screenshot of Empty View It looks like the 'editor area' is split in two, with the minimize maximize buttons in the empty area. Though I can't imagine how you can end up in this state :| - Is there anything in the error log ? - Did you ever open an editor in the empty area? In other words, did you have 2 editors opened side by side ? Which ones? - Also I can't imagine why 'Window > Reset Perspective' did not work.
This can happen in releases older than 3.7 if you have split the editor area via drag and drop of editors, and one area only contained editors that cannot be restored (e.g. compare editors). Workaround in 3.6 is to drag an editor into the empty area. *** This bug has been marked as a duplicate of bug 110684 ***
The workaround worked perfectly. I could have sworn that I tried that already, but oh well. Thanks everyone for your help.