(Sorry for forgetting the list.)
Forwarded Message
From: Juan Zhao
To: Jesse Barnes
Cc: k...@bitplanet.net
Subject: Re: [RFC] Weston sprite support
Date: Thu, 12 Jan 2012 00:09:17 +0800
On Fri, 2012-01-06 at 11:36 -0800, Jesse Barnes wrote:
> I just wanted to get a direct
2012/1/9 Jesse Barnes :
> On Fri, 6 Jan 2012 16:22:33 -0500
> Kristian Høgsberg wrote:
>> I'm concerned about make all of weston_output_repaint an output hook.
>> There's a lot of non-trivial (at least it took me a while to get it
>> right) region code in there to analyze the overlap of the surfac
On Fri, 6 Jan 2012 16:22:33 -0500
Kristian Høgsberg wrote:
> I'm concerned about make all of weston_output_repaint an output hook.
> There's a lot of non-trivial (at least it took me a while to get it
> right) region code in there to analyze the overlap of the surfaces to
> minimize the overdraw a
On Fri, 6 Jan 2012 16:22:33 -0500
Kristian Høgsberg wrote:
> I'm concerned about make all of weston_output_repaint an output hook.
> There's a lot of non-trivial (at least it took me a while to get it
> right) region code in there to analyze the overlap of the surfaces to
> minimize the overdraw a
On Fri, Jan 6, 2012 at 2:36 PM, Jesse Barnes wrote:
> I just wanted to get a direction check on this, there are still many
> open questions.
>
> The overall goal here is to be able to use overlay planes to display
> surfaces at repaint time if possible. For long lived surfaces getting
> lots of c
I just wanted to get a direction check on this, there are still many
open questions.
The overall goal here is to be able to use overlay planes to display
surfaces at repaint time if possible. For long lived surfaces getting
lots of changes, this can be a big power win since the plane blender is
a
