Policy: Consumption of raw and generated mouse events

[Mistaril]

Here is the scenario (indentation used to signify nested calls):

Code: Select all

1. mouseDown injected into System
2. mouseUpInjected into System
3.  MouseButtonUp Event generated
4.   handler consumes MouseButtonUp
5.  Timer checked, MouseClick Event generated
6.   -> MouseClick not consumed
7. -> System returns event not consumed


Ie. Even if the event handler consumed the raw event, System indicates that the event wasn't consumed. Is this by purpose and if yes, what is the reasoning?

[CrazyEddie]

This is, I think, a bug

I'll address this later today if I get time. One remaining question is, should consuming a Click event also cause the mouse button up event that triggered the click to also be consumed? I would think this should not be the case, so will apply the fix to give this behaviour.

Thanks for letting me know about this

CE.

[Mistaril]

This is, I think, a bug

I'll address this later today if I get time. One remaining question is, should consuming a Click event also cause the mouse button up event that triggered the click to also be consumed? I would think this should not be the case, so will apply the fix to give this behaviour.

IMHO, if the click is consumed, the original mouse button event should also be consumed. Otherwise there is no way for the GUI to communicate that the click has been used somehow (as the application is only feeding in raw events).

So the original event is consumed if the raw event OR any derivative events are consumed.

[CrazyEddie]

Hmmm. Decisions, decisions

I think you're probably right about this...

CE.