[PATCH weston] compositor: add a mouse motion binding type

[Giulio Camuffo]

2013/4/4 Bill Spitzak <spitzak at gmail.com>

> Kristian Høgsberg wrote:
>
>  I'm not sure if this is what Bill is getting at, but there is a
>> problem with just unconditionally triggering motion bindings.  If
>> you're moving or resizing a window and move the pointer to the corner,
>> you don't want to make that trigger an expose effect or such.
>>
>
> I was completely confusing corners of surfaces with corners of outputs,
> sorry. He is talking about fixed locations on the screen that are usually
> called "hot corners" and other terms.
>
> I think however that "hot corners" like he is describing might be better
> described as special invisible surfaces. They could be implemented by
> clients as well as by the shell, and could be subject to stacking order. It
> would also make it obvious that drags do not trigger the hot corner effect,
> though it may be triggered after the mouse is released.
>

I don't think so. Apart the added overhead on the compositor, it would not
work when there is a pointer grab active. Sometimes it would be the right
thing, like when moving a surface, some other times it would be wrong, like
when there is a popup open. The shell must always receive the motion
binding, it will then look if it is not moving some surface around or doing
some other thing and it will trigger the effect.

A thing that would allow to do what you propose is to add a new type of
surface which gets motion events even when there is a pointer grab active.
But that would mean adding new protocol and at the end it would have the
same behaviour this patch has.

Giulio
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/wayland-devel/attachments/20130404/46bc34fd/attachment.html>