[PATCH weston 1/3] Introduce pointer lock interface
ppaalanen at gmail.com
Sat Sep 20 01:00:19 PDT 2014
On Fri, 19 Sep 2014 11:00:21 -0600
"Jasper St. Pierre" <jstpierre at mecheye.net> wrote:
> On Fri, Sep 19, 2014 at 2:54 AM, Pekka Paalanen <ppaalanen at gmail.com> wrote:
> > I don't think we ever want the compositor drawing the cursor in
> > pointer-locked mode... do we? Would there be any use cases benefitting
> > from it?
> There's an additional problem here: where should the cursor be drawn? Will
> wl_relative_pointer have a set_cursor_position argument while in relative
I assumed there would be. It certainly was discussed in the past.
> I could see arguments in favor of it (ability to reuse the cursor plane),
There is nothing special with set_cursor wl_surfaces compared to
any other wl_surfaces in the protocol. Re-using a cursor plane is
not a point at all. A compositor will put any wl_surfaces on the
cursor plane whenever it can, and we do not communicate or set any
cursor-specific constraints to clients.
> but we can leave this out for now. If we want to add it back, we say that
> the cursor is always drawn in the center of the surface, unchanging, and if
> apps want to remove it, they blank it.
More information about the wayland-devel