Community
Participate
Working Groups
This is a follow up to 92638. The changes in that are very nice, but there are a few things that would make some of the new features easier to find and use (some "finishing touches" ;). 1. To detach a view, I can right click on the view tab (blue space) or the view toolbar area (gray space) to get the context menu. However, when a view becomes detached, I can only get this context menu from the toolbar area... the title bar (analogous to the tab for a floating view) gives a different context menu. 2. When you uncheck Detached for a floating view, it should redock where it was last docked. It almost seems to be random now where it redocks. 3. When you minimize a detached view, the title bar should stay in the same place. It currently seems to place them all around the screen. 4. A detached view should have icons for minimize and restore (maximize probably isn't important, but could be included). Otherwise it's not obvious that you can do this, and it's not as easy to quickly minimize and restore. 5. It could be easier to detach a tab group (not as important as above items). When docked, you can move an entire tab group, so it might be nice to similarly have options to detach view and tab group. (Also, you can detach an entire group by moving it out of workspace, but then you can only redock them one view at a time).
1) I agree that this would be nice, but it's not possible. This menu comes from the OS and (according to SWT) we can't extend it. 2) This is a known bug. The behavior was first reported in bug 88382, and bug 72060 seems to contain a fix that I will be investigating for 3.2. 3) This is the standard platform behavior for windows. Not many windows apps use minimizable tool windows, but the ones that do will behave the same. This will only change if Windows changes its native behavior. 4) This would be fixed if we changed detached views to top-level shells (bug 96428). This is a possibility but would come with many other behavioral changes. This will be investigated (but not necessarily changed) in 3.2. 5) Good suggestion. This is useful for keyboard accessibility. Since the other items are dupes, I'm renaming the PR to track this item.
Since most of these issues are covered in other bugs and DW's accessibility issues are captured in other defects I'll let this one die...
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.
