Bug 438478 - DragSource: if tree is ownerdraw, selection changes at mouse-down
Summary: DragSource: if tree is ownerdraw, selection changes at mouse-down
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 4.4   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-29 05:40 EDT by Thomas Singer CLA
Modified: 2019-11-06 12:39 EST (History)
0 users

See Also:


Attachments
Sample to reproduce (2.24 KB, application/octet-stream)
2014-06-29 05:40 EDT, Thomas Singer CLA
no flags Details
Sample to reproduce (2.24 KB, text/plain)
2014-06-29 05:40 EDT, Thomas Singer CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Singer CLA 2014-06-29 05:40:10 EDT
Created attachment 244645 [details]
Sample to reproduce

Please launch the attached snippet, put the focus in the right text field. Then click-and-hold the left mouse button on a unselected tree node. It will show the selection immediatly at the clicked node. Now comment the lines

  tree.addListener(SWT.EraseItem, listener);
  tree.addListener(SWT.MeasureItem, listener);
  tree.addListener(SWT.PaintItem, listener);

and retry - the clicked node will only get the selection changed upon mouse-up.
Comment 1 Thomas Singer CLA 2014-06-29 05:40:53 EDT
Created attachment 244646 [details]
Sample to reproduce
Comment 2 Eclipse Genie CLA 2019-11-06 12:39:04 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.

--
The automated Eclipse Genie.