Community
Participate
Working Groups
1. Open an editor. 2. Activate the 'Package Explorer'. 3. Ctrl+M 4. Click the 'Restore' button for the editor area on the side. 5. Activate the editor (it's not activated automatically, not sure if that's right or wrong, see bug 323700). 6. Ctrl+M to maximize the editor. 7. Ctrl+M to unmaximize and restore everything back to normal. 8. See now that the 'Package Explorer' has the 'Restore' icon. 9. Clicking on it does nothing. 10. Ctrl+M does nothing. 11. Double-clicking on the view's tab does nothing. At the moment, the only way to correct it that I know of is to reset your perspective.
Hmmm, this one works in 3.4...
The problem is that restoring the EA should have done an un-maximize (returning the package explorer's stack to its 'restored' state.
(In reply to comment #2) > The problem is that restoring the EA should have done an un-maximize (returning > the package explorer's stack to its 'restored' state. "un-maximize"? So would the other view stacks be brought back also?
Created attachment 177956 [details] Ensure that restoring the editor area 'unzooms'
Commotted in >20101108. Applied the patch. Now restoring the EA will un-maximize any maximized part (as we do when restoring a view stack).
Verified in I20101206-1800.
(In reply to comment #5) > Now restoring the EA will un-maximize any maximized part (as we do when > restoring a view stack). Not entirely true. When you have a view maximized and you proceed to click another view's item in the trim, that view will show up like as if it was a fast view. The perspective does _not_ get un-maximized. Also, now when you have a view maximized, you have both 'Editor Area' and 'Restore' available in the trim but they both end up doing the same thing (the view gets un-maximized). Which leads one to wonder why there is even two tool items there to begin with...
(In reply to comment #7) > (In reply to comment #5) > > Now restoring the EA will un-maximize any maximized part (as we do when > > restoring a view stack). > > Not entirely true. When you have a view maximized and you proceed to click > another view's item in the trim, that view will show up like as if it was a > fast view. The perspective does _not_ get un-maximized. That it acts like a fast view is expected and like that since the beginning. > Also, now when you have a view maximized, you have both 'Editor Area' and > 'Restore' available in the trim but they both end up doing the same thing (the > view gets un-maximized). Which leads one to wonder why there is even two tool > items there to begin with... The 'Editor Area' is the placeholder for the editor (like the view icons - if you only minimize one view it's basically the same). If editors and views would be more equal, then clicking on the 'Editor Area' would show it as fast editor - but "fast editors" are not supported.
(In reply to comment #8) > (In reply to comment #7) > > (In reply to comment #5) > > > Now restoring the EA will un-maximize any maximized part (as we do when > > > restoring a view stack). > > > > Not entirely true. When you have a view maximized and you proceed to click > > another view's item in the trim, that view will show up like as if it was a > > fast view. The perspective does _not_ get un-maximized. > That it acts like a fast view is expected and like that since the beginning. I meant that a user might not expect the entire area to be un-maximized because that doesn't happen when you click a view's icon but does happen now when you click the editor's icon. Though I suppose this might only be a problem for people who started using Eclipse when the bug surfaced itself after 3.4.
