Community
Participate
Working Groups
Build Identifier: 20100218-1602 Start with a maximized editor area filled with tabs in a window and minimized views on the side. Then close all editor tabs. After the last tab is closed the views on the side become restored. But it is possible to maximize the editor area itself without tabs afterward - this is the state the UI should behave after closing the last tab. It is annoying opening a new tab and explicitly maximizing the editor area each time. Reproducible: Always Steps to Reproduce: 1. start with a maximized editor area filled with tabs in a window and minimized views on the side 2. close all tabs 3. you see restoring the views on the side
(In reply to comment #0) > It is annoying opening a new tab and explicitly maximizing the editor area each > time. Except for this, I felt that its a feature rather than a bug :-)
I agree with Prakash. You need to use package/project explorer or a navigator to open new editor in most cases.
(In reply to comment #1) > > Except for this, I felt that its a feature rather than a bug :-) The only benefit is restoring the package explorer after closing the last tab/file in the editor. But normally if you minimize views you do it to configure your perspective. So if the workbench domineer over the user intents to configure his perspective, saving perspectives looses its meaning. At least (maybe that could be the best solution) the editor area should remember its state before closing the last tab and becoming maximized with the next tab/file opened in the editor. Also at present there's no sense maximizing the plain editor area without tabs.
(In reply to comment #3) > The only benefit is restoring the package explorer after closing the last > tab/file in the editor... I started my comment before Daniel's (but commited it later). So i accept the intent showing (navigator) views after closing the last editor tab. But i also like my perspective persistent - so returning the editor to maximized state after opening a new tab. Especially I have my navigator views opened on a second monitor and just minor views (like junit and the debug view) beside the editor area. Ohh great idea, when thinking about the 'debug view'. Please listen: the debug view ist 'pop-up'ped when starting programs in debug-mode. Also the view gets 'pop-up'ped when clicking on the thumb shown in the sidebar of the minimized perspective. But clicking into the editor area it fades out to minimized state. What's with this behavior for all minimized side-views after closing the last editor tab?
This is by design... See bug 179255 for details (where you'll see that I *tried* to make the case that we shouldn't do anything since the user explicitly set the state...;-).
(In reply to comment #5) > This is by design... Oh yes, hard work for a designer in a world of individuums that generally differs in how they receive taste by there wits. But better it is, that distinguises our brains from logical circuits. Nevertheless we should be creative enough finding a solution satisfying most of the workbench users. In any case we should leave the behavior described in bug 179255. I found two ways solving the problem, but just one of them i would take: - controlling the behavior by option [where i am shure it is not a good idea since nobody would mention this option] - lets return the editor area to maximized state after opening the next tab in it [that's it! let us use our might as an programmer to hack a more sophisticated demeanour of our software. such small things let users return for convience from testsoftware to good software] maybe changing the headline of this bug to 'when empty editor area receives first new tab, it sould return to previous state (stay minimized or become maximized)' ?
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.
