From: "Rune K. Svendsen"
I was doing some research on why I thought enabling the zoom/fade
animations added latency (a gap between releasing the launcher
button and the window appearing), and I found out that it's because,
for the first few frames, the alpha value is set to zero due to the
spring
From: "Rune K. Svendsen"
I was doing some research on why I thought enabling the zoom/fade
animations added latency (a gap between releasing the launcher
button and the window appearing), and I found out that it's because,
for the first few frames, the alpha value is set to zero due to the
spring
From: "U. Artie Eoff"
The weston-egl-ext.h include in compositor.h is not needed. Rather,
it is only needed by gles2-renderer.c. This also fixes external
module compile error since weston-egl-ext.h is not part of the
Weston SDK:
weston/compositor.h:39:28: fatal error: weston-egl-ext.h:
I just realized that this is probably not the right thing to do.
Rather, the #include "weston-egl-ext.h" should just be moved
from compositor.h to to gles2-renderer.c. I'll submit a different
patch. You choose.
U. Artie
>-Original Message-
>From: Eoff, Ullysses A
>Sent: Saturday, Februa
From: "U. Artie Eoff"
weston-egl-ext.h is included in compositor.h, therefore
needs to be installed with the weston sdk.
Signed-off-by: U. Artie Eoff
---
src/Makefile.am | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/Makefile.am b/src/Makefile.am
index bea3b5f..d925620 100644
--- a/sr
On Sat, 23 Feb 2013 12:05:20 +0100
Giulio Camuffo wrote:
> Hi
>
> > - a demo client with window decorations stitched from 4
> > non-overlapping sub-surfaces
>
> I tought i may write here the problems i've seen when doing window
> decorations this way in QtWayland:
> (http://qt.gitorious.org/~
---
src/compositor-drm.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/compositor-drm.c b/src/compositor-drm.c
index a824324..f6d030c 100644
--- a/src/compositor-drm.c
+++ b/src/compositor-drm.c
@@ -2158,7 +2158,7 @@ drm_compositor_create(struct wl_display *display,
The primary purpose of this patch is to clean up wl_closure and separate
closure storage, libffi, and the wire format. To that end, a number of changes
have been made:
- The maximum number of closure arguments has been changed from a magic number
to a #define WL_CLOSURE_MAX_ARGS
- A wl_argu
---
hw/xfree86/xwayland/xwayland-input.c |7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/hw/xfree86/xwayland/xwayland-input.c
b/hw/xfree86/xwayland/xwayland-input.c
index 39a487d..84afccc 100644
--- a/hw/xfree86/xwayland/xwayland-input.c
+++ b/hw/xfree86/xwayland/xwa
After wayland-cursor changes, this allows users to configure cursor size for
toytoolkit with the XCURSOR_SIZE environment variable as documented in weston's
man page.
---
clients/window.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/clients/window.c b/clients/window.c
inde
Presently every toolkit using wayland-cursor hard-codes or has its own
configuration for cursor size, and there is no scheme for coordination. Weston
documents the XCURSOR_SIZE environment variable as affecting Wayland programs.
This change brings that functionality into wayland-cursor so consum
Hi
> - a demo client with window decorations stitched from 4
> non-overlapping sub-surfaces
I tought i may write here the problems i've seen when doing window
decorations this way in QtWayland:
(http://qt.gitorious.org/~giucam/qt/giucam-qtwayland/commits/csd-subsurface-collage
warning: very ver
Hi,
On Fri, Feb 22, 2013 at 7:56 PM, Singh, Satyeshwar
wrote:
> The issue was that touch::down event from the compositor to client apps
> would send the previous motion events coordinates and this obviously made
> the client do the wrong thing. This happened because we were not waiting for
> a SY
13 matches
Mail list logo
