On Tue, Dec 01, 2015 at 07:51:21AM +, Daniel Stone wrote:
> Hi,
>
> On 30 November 2015 at 23:20, Peter Hutterer wrote:
> > On Mon, Nov 30, 2015 at 09:56:16PM +, Daniel Stone wrote:
> >> On 23 November 2015 at 00:19, Peter Hutterer
> >> wrote:
> >> > double pointer case when split acros
Hi,
On 30 November 2015 at 23:20, Peter Hutterer wrote:
> On Mon, Nov 30, 2015 at 09:56:16PM +, Daniel Stone wrote:
>> On 23 November 2015 at 00:19, Peter Hutterer
>> wrote:
>> > double pointer case when split across frames:
>> > p1.leave, p1.frame, *FOCUS OUT* \
>> > p2.leave, p2.frame *
On Mon, Nov 30, 2015 at 09:56:16PM +, Daniel Stone wrote:
> Hi,
>
> On 23 November 2015 at 00:19, Peter Hutterer wrote:
> > double pointer case when split across frames:
> > p1.leave, p1.frame, *FOCUS OUT* \
> > p2.leave, p2.frame *FOCUS OUT* \
> > p1.enter, p1.frame *FOCUS IN* \
> > p2
Hi,
On 23 November 2015 at 00:19, Peter Hutterer wrote:
> double pointer case when split across frames:
> p1.leave, p1.frame, *FOCUS OUT* \
> p2.leave, p2.frame *FOCUS OUT* \
> p1.enter, p1.frame *FOCUS IN* \
> p2.enter, p2.frame *FOCUS IN*
>
> double pointer case merged:
> p1.leave, p1.ent
On Sun, Nov 22, 2015 at 4:19 PM, Peter Hutterer
wrote:
>
> p1.leave, p2.leave, \
> p1.enter, p2.enter,\
> p1.frame *FOCUS TRANSITIONED*, p2.frame *FOCUS TRANSITIONED*
>
> we have the same issue where two surfaces are focused simultaneously though
> at least in this case it's detectable. I don
On Mon, Nov 23, 2015 at 10:57:01AM -0800, Bill Spitzak wrote:
> On Sun, Nov 22, 2015 at 4:19 PM, Peter Hutterer
> wrote:
>
> >
> > p1.leave, p2.leave, \
> > p1.enter, p2.enter,\
> > p1.frame *FOCUS TRANSITIONED*, p2.frame *FOCUS TRANSITIONED*
> >
> > we have the same issue where two surfaces
On Sat, Nov 21, 2015 at 02:42:25PM +, Daniel Stone wrote:
> Hi,
>
> On 20 November 2015 at 03:47, Peter Hutterer wrote:
> > On Thu, Nov 12, 2015 at 01:27:05PM +0100, Carlos Garnacho wrote:
> >> - There are grabbing situations where the focus surfaces don't really
> >> change
> >> within th
Hi,
On 20 November 2015 at 03:47, Peter Hutterer wrote:
> On Thu, Nov 12, 2015 at 01:27:05PM +0100, Carlos Garnacho wrote:
>> - There are grabbing situations where the focus surfaces don't really change
>> within the compositor (eg. dragging a window, it will probably "have" the
>> keyboard f
Hi Carlos,
On 12 November 2015 at 12:27, Carlos Garnacho wrote:
> I think it is worth to bring back some discussion on the client-side
> behavior during compositor grabs which I started a few months ago, for
> reference the thread started at:
> http://lists.freedesktop.org/archives/wayland-devel/
Hi,
On 21 November 2015 at 01:13, Bill Spitzak wrote:
> You know I have been trying to point out that the equivalent bug exists on
> wl_pointer enter/leave events for a couple years now, but all I get is
> hostility (witness recent emails). If you do manage to fix this problem,
> perhaps you coul
On Thu, Nov 19, 2015 at 7:47 PM, Peter Hutterer
wrote:
>
> we had a bit of a discussion on IRC here, this is the attempt of a summary:
> A wl_touch.enter/leave event pair makes sense for some use-cases and can
> fix
> the xdg_popup case. The idea here is that if you move between two surfaces
> *o
On Thu, Nov 12, 2015 at 01:27:05PM +0100, Carlos Garnacho wrote:
> Hey there,
>
> I think it is worth to bring back some discussion on the client-side
> behavior during compositor grabs which I started a few months ago, for
> reference the thread started at:
> http://lists.freedesktop.org/archives
Hey there,
I think it is worth to bring back some discussion on the client-side
behavior during compositor grabs which I started a few months ago, for
reference the thread started at:
http://lists.freedesktop.org/archives/wayland-devel/2015-April/021407.html
And the first patch sent was:
http://l
13 matches
Mail list logo
