Community
Participate
Working Groups
20060301 When a view part has a longer description and several toolbar action, the description is cut off and I can't a way to get the full text expect by expanding the view. See screenshot. There seems to be enough space for the description of a view part to wrap. Maybe limit it on 2 lines if you think this is a problem. There should be at least a tooltip that shows the full line.
Created attachment 35534 [details] screenshot
I've modifed this to an enhancement request... Boris, I'm guessing that this constitutes view 'management' but feel free to punt back (or forward) if you think otherwise...
any plans to fix this for 3.2?
Consider this case when looking at new e4 presentation issues.
Created attachment 143634 [details] Screen shot for text wrapping Works for me in build I20090803-1800
Created attachment 143783 [details] Another screenshot I think for the Search view had special processing was added in Eclipse 3.4 - see SearchView class from org.eclipse.search bundle; ver. 1.65; changes to #updateLabel(). In general case, in Eclipse 3.5, we don't resize control / wrap, but we do have the full description in the tooltip - see the screenshot attached.
I tend to agree with Dina's "works for me". We could add automatic resize to the description control to multiple lines. However, if we have to allocate limited screen estate between the view contents and its description, in my opinion, the view contents should get the priority.
It's not fixed. >However, if we have to allocate limited screen estate between the view contents >and its description, in my opinion, the view contents should get the priority. Most views don't show a description, so if the implementer decides to show one then it should be visible and he should not need to do tricks like the Search view.
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.