Community
Participate
Working Groups
For some views (such as Progress, Bookmarks, Search, Console) it will be great to have an option to hide their titlebar to use screen space more effective. "Hidden titlebar" can look like narrow titlebar (2..3 pixels), so doble-click will bring it back to normal size and right click will show a popup menu, that can combine all View's menus and action buttons all together. Title can be also shown in a tooltip popup. Please let me know if you'd like to see a picture of proposed enhancement.
Any chance to get this feature implemented in 3.1 release?
pictures would be helpful.
I've been looking at the existing views. It turns out that witn recent UI improvments each views status line and toolbar use screen estate quite efficiently. So, the only improvement I can think of is to hide all tabs in a current tabgroup. It may look like wider border on top of the view tab group and tabs will appear back when user move mouse in that border area. When tabs are hidden, all icons should be shown on view toolbar.
Created attachment 18000 [details] Original progress view
Created attachment 18001 [details] Possible visual appearance of single view with all controls/toolbars hidden.
I've added some atachments to illustrate possibilities for hiding toolbar and other view area controls.
How would you expect it to behave if there were multiple views (each with their own tab) docked together?
One reasonable option would be to disable this feature if area has more then one view. Second option would be to put some kind of clickable "shadows" for each tab. These shadows could have mouse rollover pop-up. I think 1st option will be sufficient, because the whole idea is to make some particular view always visible, so it should use all space as efficient as possible.
Reassigning bugs in component areas that are changing ownership.
Remy is now responsible for watching the [ViewMgmt] category.
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.
