Re: [PATCH weston 3/3] compositor: don't map surfaces without a buffer

2017-02-21 Thread Pekka Paalanen
On Fri, 3 Feb 2017 16:10:39 +0100 Emilio Pozuelo Monfort wrote: > We were calling weston_surface::committed on surfaces with > no buffer attached. Stop doing that, since surface::committed > will map the surfaces and put them in a visible layer. That may > not be a problem for a single surface a

Re: [PATCH weston 3/3] compositor: don't map surfaces without a buffer

2017-02-21 Thread Pekka Paalanen
On Fri, 3 Feb 2017 09:27:18 -0600 Derek Foreman wrote: > On 03/02/17 09:10 AM, Emilio Pozuelo Monfort wrote: > > We were calling weston_surface::committed on surfaces with > > no buffer attached. Stop doing that, since surface::committed > > will map the surfaces and put them in a visible layer.

Re: [PATCH weston 3/3] compositor: don't map surfaces without a buffer

2017-02-03 Thread Emilio Pozuelo Monfort
On 03/02/17 16:27, Derek Foreman wrote: > On 03/02/17 09:10 AM, Emilio Pozuelo Monfort wrote: >> We were calling weston_surface::committed on surfaces with >> no buffer attached. Stop doing that, since surface::committed >> will map the surfaces and put them in a visible layer. That may >> not be a

Re: [PATCH weston 3/3] compositor: don't map surfaces without a buffer

2017-02-03 Thread Derek Foreman
On 03/02/17 09:10 AM, Emilio Pozuelo Monfort wrote: We were calling weston_surface::committed on surfaces with no buffer attached. Stop doing that, since surface::committed will map the surfaces and put them in a visible layer. That may not be a problem for a single surface as it wouldn't be visi

[PATCH weston 3/3] compositor: don't map surfaces without a buffer

2017-02-03 Thread Emilio Pozuelo Monfort
We were calling weston_surface::committed on surfaces with no buffer attached. Stop doing that, since surface::committed will map the surfaces and put them in a visible layer. That may not be a problem for a single surface as it wouldn't be visible anyway because it's got no contents, but it is a p