Bug 73175

Summary: [DetachedWindows] Add support for DetachedWindow snapping
Product: [Eclipse Project] Platform Reporter: Cory Turner <cturner>
Component: UIAssignee: Platform UI Triaged <platform-ui-triaged>
Status: ASSIGNED --- QA Contact:
Severity: enhancement    
Priority: P5 CC: baison_hever, michaelvanmeekeren, sxenos
Version: 3.0Keywords: helpwanted
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
PerspectiveHelper.java patch none

Description Cory Turner CLA 2004-09-02 14:53:17 EDT
Add a feature that allows DetachedWindows to "snap" to the edge of monitors, or
the edge of other shells.
Comment 1 Cory Turner CLA 2004-09-02 14:58:45 EDT
Created attachment 14365 [details]
PerspectiveHelper.java patch

Here is a quick attempt at this feature. The intial implementation demonstrates
the expected behaviour, but suffers from a few bugs. 

1) Tracking follows the cursor instead the expected dragRectangle
2) Snapping can move the window in the wrong axis when moving from one window
to another. (Dragging off the workbench may cause the window to snap to the
right edge of WorkbenchWindow even though you were half way across). 
3) When within snapping distance of any edge, it will snap to any available
line. For example, if you have a workbenchwindow open, and a detached view.
Dragging the view along the bottom of the window will work fine until it hits
what would be the left edge of the WorkbenchWindow if you followed it down. It
snaps here.

The algorithm may also need performance tuning.
Comment 2 Stefan Xenos CLA 2005-05-26 04:45:40 EDT
This is a very good idea, but the implementation will have to change
considerably now that we're dragging using the OS trim.
Comment 3 Paul Webster CLA 2006-09-28 11:00:30 EDT
There are currently no plans to work on this feature.

PW
Comment 4 Denis Roy CLA 2007-06-22 09:32:42 EDT
Changes requested on bug 193523
Comment 5 Eclipse Webmaster CLA 2019-09-06 15:38:12 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.