Bug 105721 - [Presentations] easier minimize of views
Summary: [Presentations] easier minimize of views
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC Linux
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2005-08-01 16:07 EDT by Alvin Thompson CLA
Modified: 2019-09-06 16:10 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alvin Thompson CLA 2005-08-01 16:07:26 EDT
i regularly leave the views at the bottom of the screen minimized, and only
activate them when i need them. the problem is that when i'm done with the view,
i have to move my mouse all the way back to the right and click on that tiny
minimize icon (i'm very lazy).

it would be nice to have an option where if you click on a tab for a view that's
already active, the view is minimized again. since the mouse is already in that
area from clicking on the tab in the first place, the distance is much shorter.
plus, you have a much fatter target to hit with the mouse.
Comment 1 Boris Bokowski CLA 2005-08-09 18:48:47 EDT
Have you tried using fast views? (To turn a view into a fast view, right-click
on its tab and select "Fast View".)
Comment 2 Alvin Thompson CLA 2005-08-09 19:17:37 EDT
yup, but i like the regular view better. 
Comment 3 kgrot CLA 2005-09-20 12:05:47 EDT
FYI, the "auto-open" behavior suggested in 88239 might solve this problem as well.
Comment 4 Paul Webster CLA 2006-09-28 11:01:11 EDT
There are currently no plans to work on this feature.

PW
Comment 5 Denis Roy CLA 2007-06-22 09:33:02 EDT
Changes requested on bug 193523
Comment 6 Eclipse Webmaster CLA 2019-09-06 16:10:33 EDT
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.