Re: [PATCH weston v3 1/6] compositor: Untangle mapedness from outputs

2016-07-01 Thread Pekka Paalanen
On Thu, 30 Jun 2016 12:50:42 -0700 Bryce Harrington wrote: > mapedness isn't a word ;-) > > (Neither is mappedness really... You'll likely need to reword the > commit title entirely. The third sentence in your commit message is > probably a good starting point if you can boil it down.) Hi all

Re: [PATCH weston v3 1/6] compositor: Untangle mapedness from outputs

2016-07-01 Thread Armin Krezović
On 30.06.2016 21:50, Bryce Harrington wrote: > mapedness isn't a word ;-) > > (Neither is mappedness really... You'll likely need to reword the > commit title entirely. The third sentence in your commit message is > probably a good starting point if you can boil it down.) > After a discussion

Re: [PATCH weston v3 1/6] compositor: Untangle mapedness from outputs

2016-06-30 Thread Bryce Harrington
mapedness isn't a word ;-) (Neither is mappedness really... You'll likely need to reword the commit title entirely. The third sentence in your commit message is probably a good starting point if you can boil it down.) On Thu, Jun 30, 2016 at 06:04:28AM +0200, Armin Krezović wrote: > Currently,

[PATCH weston v3 1/6] compositor: Untangle mapedness from outputs

2016-06-29 Thread Armin Krezović
Currently, weston assumes a surface/view is mapped if it has an output assigned. In a zero outputs scenario, this isn't really desirable. This patch introduces a new flag to weston_surface and weston_view, which has to be set manually to indicate that a surface/view is mapped. v2: - Remove usage