Bug 131122

Summary:	[Presentations] Make view borders "snap" to each other when dragging
Product:	[Eclipse Project] Platform	Reporter:	Justin Berstler <bjustin>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	ASSIGNED ---	QA Contact:
Severity:	enhancement
Priority:	P5	Keywords:	helpwanted
Version:	3.2
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Justin Berstler

2006-03-09 11:32:25 EST

Ok... so maybe I've got some sort of personality disorder or something, but I *really* like it when my views line up just right.  For example, if you reset the Resource Perspective, it (mildly) drives me nuts that the top of the Outline View does not line up with the top of the Tasks View.  And while I am not suggesting that the Resource Perspective's layout should be modified to do so, I suggest that you make it easier for crazy people like myself to get them to line up just right.

What I propose is that while you are resizing a view (e.g. the Outline view in the Resource Perspective) that if the border being dragged comes within N-pixels (say 3-5) of another view's similarly-oriented border (e.g. the top of the Tasks view in the Resource Perspective) that the size of the view being dragged *snaps* to line up exactly with that other similarly-oriented border. And then if the user keeps dragging (in either direction) the border of the view be outside of that N-pixel snap range, then the view border will un-snap and become free again.

Comment 1 Paul Webster

2006-09-28 11:01:40 EDT

There are currently no plans to work on this feature.

PW

Comment 2 Denis Roy

2007-06-22 09:33:23 EDT

Changes requested on bug 193523

Comment 3 Eclipse Webmaster

2019-09-06 15:30:06 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.

Comment 4 Eclipse Webmaster

2019-09-06 15:34:49 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.