On 3/07/10 02:22 , Keith Packard wrote:
On Fri, 2 Jul 2010 15:31:19 +1000, Peter Hutterer<[email protected]>
wrote:
Having miPointerMove and miPointerMoved is confusing, especially since both
do the same thing bar the event delivery. Also, miPointerMove calls
miPointerMoved which indicates some confusion in the temporal alignment of
cause and effect.
<Bikeshed>
Should we rename miPointerMove too? Perhaps miPointerMoveWithEvent and
miPointerMoveWithoutEvent?
</bikeshed>
meh.
I think it's fine as it is. moving the pointer always generates an
event, the exception being miPointerMoveNoEvent, explicitly labeled so.
Cheers,
Peter
_______________________________________________
[email protected]: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: http://lists.x.org/mailman/listinfo/xorg-devel
