On Thu, 6 Sep 2012 11:10:39 -0400
Kristian Høgsberg wrote:
> On Wed, Sep 05, 2012 at 09:36:59AM +0300, Pekka Paalanen wrote:
> > Some color formats are naturally opaque: RGB, XRGB, YUV formats without
> > A channel. For these, automatically set the opaque region to whole
> > surface.
> >
> > Not
On Thu, 6 Sep 2012 11:25:20 -0400
jegde jedge wrote:
> Thank you so much, that did the trick!
>
> Next Question :)
> On the same code, on the same hardware...
> I am getting the glut 60 fps limit when running my app using the glut
> front end via
> gnome and X.
> I am getting ~24 fps using the s
On Thu, 6 Sep 2012 22:40:49 -0700
Mikalai Kisialiou wrote:
> Next time you guys decide to update the documentation, it may probably make
> sense to explicitly list key advantages of Wayland/Weston, like the one
> that the clients are completely independent unlike X where they can screw
> around.
I switched from X to Weston a couple days ago. The only thing
I've needed X for in that time was playing a movie, and thanks to
Alexander Preisinger I could've compiled mplayer with native Wayland
support instead. Totem mostly works, but I can't get it to go into
fullscreen mode (since XWayland m
Pekka Paalanen wrote:
Please, carefully read 'man xorg.conf' on how xorg.conf.d works. I
assume you will want to have xwayland.conf.d replacing xorg.conf.d,
just like you suggest xwayland.conf replaces xorg.conf.
I get it now. Well they certainly made a mess of something that should
be simple
I forgot to mention.
its on 945GME
glut 60 fps uses 17%cpu
wayland 24 fps uses 3% cpu
I am hoping for an apples to apples. !
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/wayland-devel
Thank you so much, that did the trick!
Next Question :)
On the same code, on the same hardware...
I am getting the glut 60 fps limit when running my app using the glut
front end via
gnome and X.
I am getting ~24 fps using the simple-egl front end on top of wayland.
I also noticed the display using
On Thu, Sep 06, 2012 at 03:23:28PM +0200, Philipp Brüschweiler wrote:
> Use 0 as transparent pixel. This is needed when using premultiplied
> alpha.
Thanks, committed.
Kristian
> ---
> clients/wscreensaver-glue.c | 6 +++---
> 1 Datei geändert, 3 Zeilen hinzugefügt(+), 3 Zeilen entfernt(-)
>
>
On Wed, Sep 05, 2012 at 09:36:59AM +0300, Pekka Paalanen wrote:
> Some color formats are naturally opaque: RGB, XRGB, YUV formats without
> A channel. For these, automatically set the opaque region to whole
> surface.
>
> Note:
> If a client first sends a buffer with opaque color format, and then
This theme is loaded when the specified cursor theme can not be found.
These cursors are extracted from the xorg sources and transformed into
xpm files by a small helper program (commited separately).
---
cursor/bottom_left_corner.xpm | 48 ++
cursor/bottom_right_corner.xpm | 48 ++
On Thu, 6 Sep 2012 15:23:28 +0200
Philipp Brüschweiler wrote:
> Use 0 as transparent pixel. This is needed when using premultiplied
> alpha.
> ---
> clients/wscreensaver-glue.c | 6 +++---
> 1 Datei geändert, 3 Zeilen hinzugefügt(+), 3 Zeilen entfernt(-)
>
> diff --git a/clients/wscreensaver-g
Use 0 as transparent pixel. This is needed when using premultiplied
alpha.
---
clients/wscreensaver-glue.c | 6 +++---
1 Datei geändert, 3 Zeilen hinzugefügt(+), 3 Zeilen entfernt(-)
diff --git a/clients/wscreensaver-glue.c b/clients/wscreensaver-glue.c
index a548599..55d0a8c 100644
--- a/clients
On Thu, 06 Sep 2012 12:41:15 +0200
Birin Sanchez wrote:
> Hi Pekka,
>
> I gave this clipping algorithm a try and I found a weird behaviour that
> I don't know if it is expected of not. See attachment 1.
>
> And this is how to reproduce it:
>
> * Move the clipping area to get it side by side
13 matches
Mail list logo