Bug 267355 - Drag and drop: Tree does not update vertical scrollbar when auto-scrolling
Summary: Drag and drop: Tree does not update vertical scrollbar when auto-scrolling
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Felipe Heidrich CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 284840 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-03-06 08:25 EST by Markus Keller CLA
Modified: 2019-09-06 16:05 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Keller CLA 2009-03-06 08:25:50 EST
I20090304-0834

- launch DNDExample
- on the right side, select Tree and FEEDBACK_SCROLL
- expand some tree items such that vertical scrollbar appears
- drag something over the bottom of the tree
=> tree scrolls, but vertical scrollbar is not updated (only after I release the mouse). Works fine for a table or when a tree item is auto-expanded.
Comment 1 Felipe Heidrich CLA 2009-03-09 13:26:59 EDT
Steve, this only happens on Trees with columns.
We can fix it by hiding and showing the scrollbar:

OS.ShowScrollBar (hwndParent, OS.SB_VERT, false);
OS.ShowScrollBar (hwndParent, OS.SB_VERT, true);

That works by causes flashing.

Do know of any other say to force the scrollbar to draw without side effects ?

(note, the code is wrong, it first needs to test if the scrollbar is visible before doing anything.) 
Comment 2 Steve Northover CLA 2009-03-09 14:12:06 EDT
Please investigate Tree.showItem().
Comment 3 Felipe Heidrich CLA 2009-03-09 14:34:56 EDT
(In reply to comment #2)
> Please investigate Tree.showItem().

It causes cheese
Comment 4 Steve Northover CLA 2009-03-09 15:10:35 EDT
Then we have a bug.
Comment 5 Felipe Heidrich CLA 2009-07-28 09:23:22 EDT
*** Bug 284840 has been marked as a duplicate of this bug. ***
Comment 6 Eclipse Webmaster CLA 2019-09-06 16:05:31 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.