Bug 320092 - TableViewer doesn't scroll horizontally while dragging and moving columns
Summary: TableViewer doesn't scroll horizontally while dragging and moving columns
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 4.0   Edit
Hardware: PC Windows 7
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-16 07:33 EDT by Helmut Neubauer CLA
Modified: 2019-11-08 04:40 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Helmut Neubauer CLA 2010-07-16 07:33:35 EDT
Build Identifier: I20100608-0911

The TableViewer doesn't scroll horizontalyl while dragging and moving a column in direction to the other invisible columns. This happens only on Windows (Max and Linux seems OK). 

Reproducible: Always

Steps to Reproduce:
Use a TableViewer in your application with a lot of columns (there must be some invisible ones) and try to drag and move a column in direction to the insivible ones. Normally, there should be an auto scrolling, but using Windows there is no one. 
2.
3.
Comment 1 Grant Gayed CLA 2011-03-24 10:19:17 EDT
Snippet:

public static void main(String[] args) {
    final Display display = new Display();
    Shell shell = new Shell(display);
    shell.setBounds(10,10,200,200);
    shell.setLayout(new FillLayout());
    Tree tree = new Tree(shell, SWT.NONE);
    tree.setHeaderVisible(true);
    for (int i = 0; i < 20; i++) {
        TreeColumn column = new TreeColumn(tree, SWT.NONE);
        column.setText("col" + i);
        column.setWidth(50);
        column.setMoveable(true);
    }

    shell.open();
    while (!shell.isDisposed()) {
    	if (!display.readAndDispatch()) display.sleep();
    }
    display.dispose();
}
Comment 2 Lars Vogel CLA 2019-11-08 04:40:24 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.

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.

If the bug is still relevant please remove the stalebug whiteboard tag.