Re: [PATCH] compositor: Don't use empty bounding boxes for output assigninment

2012-09-12 Thread Kristian Høgsberg
On Tue, Sep 11, 2012 at 05:37:29PM +0300, Ander Conselvan de Oliveira wrote: > From: Ander Conselvan de Oliveira > > When weston_surface_assign_output() is called for an unmap'd surface, > its bounding box is empty causing no output to be assigned. This later > causes calls to weston_surface_sche

Re: [PATCH] compositor: Don't use empty bounding boxes for output assigninment

2012-09-12 Thread Ander Conselvan de Oliveira
On 09/12/2012 09:15 AM, Pekka Paalanen wrote: On Tue, 11 Sep 2012 17:37:29 +0300 Ander Conselvan de Oliveira wrote: From: Ander Conselvan de Oliveira When weston_surface_assign_output() is called for an unmap'd surface, its bounding box is empty causing no output to be assigned. This later c

Re: [PATCH] compositor: Don't use empty bounding boxes for output assigninment

2012-09-11 Thread Pekka Paalanen
On Tue, 11 Sep 2012 17:37:29 +0300 Ander Conselvan de Oliveira wrote: > From: Ander Conselvan de Oliveira > > When weston_surface_assign_output() is called for an unmap'd surface, > its bounding box is empty causing no output to be assigned. This later > causes calls to weston_surface_schedule_

[PATCH] compositor: Don't use empty bounding boxes for output assigninment

2012-09-11 Thread Ander Conselvan de Oliveira
From: Ander Conselvan de Oliveira When weston_surface_assign_output() is called for an unmap'd surface, its bounding box is empty causing no output to be assigned. This later causes calls to weston_surface_schedule_repaint() to schedule no repaint at all. This is the cause of surfaces not being s