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 Jan 9, 2012, at 12:43 AM, Pekka Paalanen wrote:
>
> Note, that even 3D projective transformations are just a subset.
> Nothing should prevent arbitrary non-linear transformations in the
> compositor, if they make any sense. How about projection on a sphere,
> like in a planetarium? In case so
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
From: Alex Wu
mainly send a configure event to the client
Signed-off-by: Juan Zhao
Signed-off-by: Alex Wu
---
src/shell.c | 48
1 files changed, 48 insertions(+), 0 deletions(-)
diff --git a/src/shell.c b/src/shell.c
index d12bc1a..b93bfa3
From: Alex Wu
For some appliation(e.g. xbmc) wanting actual fullscreen effect, compositor
should change the
display mode to match the app UI rectangle. We add 2 parameters to
set_fullscreen in order to
let client to choose the appropriate way to deal with dismatch between the
client's surface
From: Alex Wu
add one interface to let the client notify the compositor the maximised
operation,
and then the compositor will send a configure event back to the client
Signed-off-by: Juan Zhao
Signed-off-by: Alex Wu
---
protocol/wayland.xml |2 ++
1 files changed, 2 insertions(+), 0 de
From: Alex Wu
framerate: the expected framerate which will be used as refresh value to choose
display mode.
flags: indicate how to deal with resolution dismatch.
support three methods:
"SCALE" means the compositor will scale the surface to the fullscreen.
"FORCE" means changing the scr
On Fri, 06 Jan 2012 10:55:22 -0800
Bill Spitzak wrote:
> This is why I would prefer that the clients do full screen by finding
> out the size of the monitor and directly setting the transform to how
> they fill the screen. Then the client knows exactly what transform is
> happening, and can co
