Description Andrzej Cichocki 2007-03-09 06:04:53 EST

Build ID: M20070212-1330

The busy cursor / progress dialog are provided by the Eclipse workbench progress service.

Steps To Reproduce:

1. Run the attachment as an Eclipse RCP application.
2. Open 1 view and 1 editor using the buttons provided.
3. Click into the cell editor in the editor.
4. Click on the item in the view.

There is a mouse listener on the tree in the view that logs mouse events to stderr.

On GTK:

Quick click:

  You get both a mouseDown and a mouseUp event, at the respective times that the mouse goes down and comes up. This is as expected.

Press, wait for dialog to show, release:

  You get the mouseDown event but no mouseUp event. The lack of mouseUp is unfortunate, but not a significant problem for us.

Press, wait for dialog to close, release:

  As for quick click: A mouseDown and a mouseUp event, at the respective times that the mouse goes down and comes up.

On XP and Vista Aero:

Quick click:

  You only get a mouseDown event, and it is received just after the progress dialog has closed. This is very strange, as it was action of pressing the mouse down that triggered the dialog to display.

Press, wait for dialog to show, release:

  As for quick click: A mouseDown event just after the dialog has closed.

Press, wait for dialog to close, release:

  A mouseDown event just after the dialog closes, and a mouseUp event when the mouse comes up.

On XP in VMware:

Quick click:

  mouseDown and mouseUp, both just after the dialog closes.

Press, wait for dialog to show, release:

  As for quick click: mouseDown and mouseUp just after the dialog closes.

Press, wait for dialog to close, release:

  mouseDown and mouseUp just after the dialog closes, and *another* mouseUp event when the mouse actually comes up. Again, very strange -- how did we get two mouseUp events?

Issues:

There should always be a mouse down event. There should be at most one mouse up event. There should not be a delay between the mouse going down and the mouse down event being fired, nor between the mouse coming up and the mouse up event being fired. The inconsistency across platforms should also be addressed.