Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 66736

Summary:	[ViewMgmt] View can be dropped in two different ways on same edge
Product:	[Eclipse Project] Platform	Reporter:	Nick Edgar <n.a.edgar>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P5	Keywords:	helpwanted
Version:	3.0
Target Milestone:	---
Hardware:	PC
OS:	Windows 2000
Whiteboard:	stalebug

Description Nick Edgar

2004-06-11 13:43:41 EDT

build I20040611-0800

- in the browser example, open the history view
- drag it into the same folder as the browser view
- drag it to the left edge of the stack until you get the left arrow
- drop it
- it splits the area evenly
- drag it back so there's a single stack again
- drag it to the left edge of the window until you get the right arrow
- drop it
- it splits the area 1/3, 2/3

If dropping on the same edge, there should be only one way of doing it.

Comment 1 Stefan Xenos

2005-04-01 19:56:42 EST

Right now, all the ratios are worked out using heuristics. For example, if you
create a split by dropping A onto the edge of B, we need to decide how much
space goes to A and how much to B. Current heuristics are:

- view/view -> 50/50
- editor/editor -> 50/50
- view/editor area -> 25/75
- editor/editor area -> 50/50
- view/workbench page -> 25/75

In the use-case described above there are only 2 parts, so there is no
interesting distinction between a view/view split and a view/workbench page
split and the different ratios seem silly.

I would suggest fixing this by removing these heuristics and instead set things
up so that the dropped part always either retains one of its dimensions (in
pixels) or uses 50% of the space, whichever is smaller.

Comment 2 Stefan Xenos

2005-04-01 19:57:07 EST

Didn't mean to flag as WONTFIX. :-)

Comment 3 Boris Bokowski

2009-11-11 17:32:23 EST

Remy is now responsible for watching the [ViewMgmt] category.

Comment 4 Eclipse Webmaster

2019-09-06 16:11:58 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 5 Eclipse Genie

2022-01-25 14:30:51 EST

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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.