[PATCH] selection: send selection events to all connected clients

Pekka Paalanen ppaalanen at gmail.com
Tue Apr 16 11:43:42 PDT 2013


On Tue, 16 Apr 2013 08:41:16 -0700
Bill Spitzak <spitzak at gmail.com> wrote:

> On 04/15/2013 11:54 PM, Pekka Paalanen wrote:
> 
> > Drag & drop obviously has to use pointer focus, so no problem there.
> 
> I guess I don't see that. I thought it was very common for the focus to 
> remain on the dragged-from application, especially when click-to-type is 
> used. It sounds like you are requiring focus to move the the dragged-to 
> client.

Pointer focus, not keyboard focus.

> > Yes. I assumed a click event, like middle button to paste, would first
> > assign the keyboard focus, which causes the selection events to be
> > sent, and then send the actual input event.
> 
> I don't like the idea of being unable to do a middle-mouse click without 
> moving the keyboard focus. And it sounds like the underlying design 
> *requires* clicks to move keyboard focus, even for non-paste clicks. 
> This is really bad because it hugely restricts possible user interface 
> ideas.
> 
> The client must be allowed to decide if a click will move the keyboard 
> focus to it, and whether or not a click will raise it's window.

As you know, all that is still in the air, and we have no protocol
for it. We only have what Weston currently implements. Pointer
focus and keyboard focus are Wayland core concepts, but when to
assign keyboard focus is not written in stone (or core). Maybe it's
also possible from the core protocol point of view to offer
selection also without keyboard focus, and if it is, it will
probably be the shell's definition when to do that.

> Requiring that the client have recently gotten a keyboard or mouse click 
> or a drag & drop event might be ok, though. This could be done by 
> marking the selection request with the serial of an event.

Keyboard events cannot come without keyboard focus, so that's
sorted. Drag & drop is irrelevant for selection. Just the
mouse-paste without focusing is at question whether it is needed or
supportable.


Thanks,
pq


More information about the wayland-devel mailing list