Bug 239927 - [Linux]TreeViewer's context menu is not refreshed correctly.
Summary: [Linux]TreeViewer's context menu is not refreshed correctly.
Status: CLOSED DUPLICATE of bug 79925
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.4   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Bogdan Gheorghe CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 239748
  Show dependency tree
 
Reported: 2008-07-08 04:23 EDT by Xingsheng Zhu CLA
Modified: 2009-12-23 10:41 EST (History)
3 users (show)

See Also:

Attachments
The java class with main method to reproduce (4.53 KB, text/x-java)
2008-07-08 04:23 EDT, Xingsheng Zhu 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 Xingsheng Zhu CLA 2008-07-08 04:23:16 EDT 
Created attachment 106790 [details]
The java class with main method to reproduce

Build ID: I20080617-2000

Steps To Reproduce:
1.Run the attached test application in Linux.
2.Right click the first item till the context menu shown.
3.Right click the second item.
Expected result:
The context menu of the second item shows its text "BBBbbb"

Actual result:
It shows the first item's "AAAaaa".Actually, if you right click the items like this:the first one, the second one,the first one, the second one.....it will always show the wrong context menu.
Comment 1 Praveen CLA 2009-12-07 03:00:24 EST 
The problem is reproducible. This is caused due to the MenuDetect event preceding the MouseDown event.
The menu is actually constructed in the MouseDown event, thus causing the previous menu to be displayed in the MenuDetect event (as this will be referencing to the menu constructed on the different object).
Since the root cause of this issue is similar to the problem reported in bug#79925, this can be marked as a duplicate of bug#79925.
Comment 2 Praveen CLA 2009-12-23 10:41:14 EST 

*** This bug has been marked as a duplicate of bug 79925 ***