Bug 141114 - Tree: immoveable columns can be moved
Summary: Tree: immoveable columns can be moved
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 minor with 5 votes (vote)
Target Milestone: ---   Edit
Assignee: Steve Northover CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-10 14:26 EDT by Nigel Westbury CLA
Modified: 2019-09-06 16:15 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nigel Westbury CLA 2006-05-10 14:26:03 EDT
A column in a Tree control with the moveable flag set to false cannot itself be dragged.  However, other columns can be dragged across it, achieving the same effect.  In the tree view in particular it would seem to me to be a common requirement that the first column is fixed, and dragging another column to be the first column would often result in a strange buggy looking view.

A more useful interpretation of an immoveable column would be that no column can be dragged across it.  Such columns thus act as a sort of barrier.  I can think of no user case which has a requirement that a column cannot be dragged itself but should be able to be moved by dragging other columns across it.

It might also be possible to control column movement by listening for the SWT.Move event and setting the doit flag off.  However, there is no information placed in the event that makes this possible.  The easiest from the Tree control user's point of view would be if the new column index were available, but if even just the x field were set then the new column index could be calculated.
Comment 1 Steve Northover CLA 2006-05-10 14:33:01 EDT
We can't change the current behavior but we may be able to use a doit flag to stop the column drag in the future.
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:15:03 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.