Bug 216330 - In-place edit in Tree has inconsistent MouseEvent between platforms
Summary: In-place edit in Tree has inconsistent MouseEvent between platforms
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Steve Northover CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 176807 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-01-23 14:21 EST by Duong Nguyen CLA
Modified: 2019-09-06 15:31 EDT (History)
2 users (show)

See Also:

Attachments
Sample code to show MouseEvents in tree (4.38 KB, application/octet-stream)
2008-01-23 14:25 EST, Duong Nguyen CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Duong Nguyen CLA 2008-01-23 14:21:59 EST 
When an item in a tree is selected to have in place editing, the mouse events are fired differently depending on the platform that you're using.

On Windows, when a tree item is clicked and an in-place editor takes focus, the MouseDown event is sent to the Tree and MouseUp is sent to the Text widget.

On GTK, when a tree item is clicked and an in-place editor takes focus, the MouseDown and MouseUp events are both sent to the Tree.
Comment 1 Duong Nguyen CLA 2008-01-23 14:25:17 EST 
Created attachment 87687 [details]
Sample code to show MouseEvents in tree
Comment 2 Duong Nguyen CLA 2008-01-23 14:27:52 EST 
Steps:
- run the example
- select an item and cause the in-place editor to appear
- in the console you will only see the MouseDown event on Windows. On GTK, you see both the MouseDown and MouseUp events.
Comment 3 Duong Nguyen CLA 2008-01-23 14:31:48 EST 
*** Bug 176807 has been marked as a duplicate of this bug. ***
Comment 4 Steve Northover CLA 2008-04-21 15:33:49 EDT 
This just seems like a platform difference to me (that we won't work around).  Is there an application code problem here that is needed to be worked around?
Comment 5 Eclipse Webmaster CLA 2019-09-06 15:31:41 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.