Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 138642 - Table Mouse events fires after EraseItem event.
Summary: Table Mouse events fires after EraseItem event.
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Steve Northover CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-26 10:42 EDT by Cioroga Ilie Lucian CLA
Modified: 2019-09-04 03:03 EDT (History)
0 users

See Also:

Attachments
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 Cioroga Ilie Lucian CLA 2006-04-26 10:42:52 EDT 
I am trying to create my own Tree/TableCursor to work with Tree/TableViewer and there seems to be a minor problem with events. I'm using a MouseDown event to determine the selected cell and a EraseItem event to block and override the default selection drawing. The problem is that it seems that EraseItem fires prior to MouseDown (which I belive is not logical), so I'm forced to do a setSelection in order to force the repaint. What I get is 3 events instead of 2: EraseItem-MouseDown-EraseItem instead of MouseDown-EraseItem. This often results in a minor screen flickering.

I wouldn't have reported this as a bug if I haven't noticed that Tree events are not fired in the same way. Actualy, they are fired in what I think to be the correct way (MouseDown than EraseItem). Using almoust the same implementation the screen doesn't flickers on TreeCursor.

Would be nice if this could be fixed as I'm quite sure it requires minor modifications.
Comment 1 Steve Northover CLA 2006-05-10 13:45:56 EDT 
Not for 3.2.  Sorry about that but it's too late to change this now.  Ping me early in the 3.3 release cycle.
Comment 2 Lars Vogel CLA 2019-09-04 03:03:53 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 and remove the stalebug whiteboard tag. 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.

-