| Summary: | [DetachedViews] Trim looks odd on detached windows | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Ed Burnette <ed.burnette> | ||||
| Component: | UI | Assignee: | Eric Moffatt <emoffatt> | ||||
| Status: | RESOLVED DUPLICATE | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | ||||||
| Version: | 3.2 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Ed Burnette
Created attachment 32089 [details]
Screenshot of a detached view on Windows XP in 3.2M4
There are 5, count'em, 5 "x"'s in this view, and two of them will close the window. As long as the detached window is not stacked, why not use the view title for the window title and do away with the tab and it's close button?
Ed, this is the way they worked on 3.1...a single detached view gets treated as being part of a 'stack' (and all that implies). See bug 120921 for a somewhat more limited enhancement request. I'm currently investigating this whole area with an eye to trying to consolidate the 'non-sashed' view handling (i.e. includes both detached and fast view handling) as I have a fair variety of suggestions on enhancements in this area. Once I've figured out a general approach I'll open a 'work item' defect which will reference this and all the other related defects to allow a single point of info capture...not likely for M5 however (I'm fairly booked...;-). It may be what 3.1 did but it still looks odd don't you think? I know it's done that way to allow for a stack but I suspect the most common use case is to not stack them. Are you sure you have the right bug number in your comment? It didn't seem related. Oooops, the correct number is bug 120910...sorry about hte confusion. *** This bug has been marked as a duplicate of bug 120910 *** |