On Mon, 15 Apr 2013 12:39:21 -0700 Bill Spitzak <spit...@gmail.com> wrote:
> Pekka Paalanen wrote: > > > Alright. I'm not too familiar with toolkits, so could you explain > > why toolkits need to access the selection at arbitrary times > > (specifically while unfocused), instead of only as a response to > > direct user input (which in all relevant cases assigns the focus > > first)? > > I sure hope you don't mean keyboard focus, right? I'm not sure whether it uses keyboard or pointer focus, and I couldn't find it in the code on a glimpse. > There must be the ability to cause a paste by using a pointing device > without moving the keyboard focus. An obvious reason is for drag & > drop, but is also often used for middle-mouse paste in a > point-to-type environment, and likely wanted if there are alternative > input devices. Drag & drop obviously has to use pointer focus, so no problem there. Selection could perhaps be different. > However requiring that the pointing device be above one of the client > surfaces and an actual click-like event (rather than a move) is > probably ok. I believe this is what you mean by "assign focus", right? 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 have to say that I have not verified this from the code. Thanks, pq _______________________________________________ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel
