[PATCH 4/4] compositor: fix repaint on first wakeup

wlsc_compositor_fade() ends up in wlsc_compositor_schedule_repaint(), which is a no-op if compositor is SLEEPING. On wakeup, first set status to ACTIVE, then call wlsc_compositor_fade() to start and actually show the animation. Before, fade was called first, which reset the animation, but did not

[PATCH 3/4] compositor: remove idle_inhibit optimization

With the idle_inhibit optimization, wlsc_compositor_wake() is a no-op if idle_inhibit > 0. When the shell is waking up the compositor from SLEEPING state as an indirect response to input activity, it does not work. The call path is: notify_key() / notify_button() wlsc_compositor_idle_inhib

[PATCH 2/4] compositor: let the shell wake up the compositor

From: Kristian Høgsberg When compositor enters SLEEPING state, the shell plugin goes locked. If compositor wakes up itself, it will fade in while the shell may not yet have a lock surface to show. Fix this by assigning wake-up to be called from the shell, if the compositor is SLEEPING. The shell

[PATCH 1/4] desktop-shell: screen locking protocol

Add protocol and functions for supporting screen locking, triggered by activity timeout. After activity timeout, compositor starts the fade to black, and then enters SLEEPING state. At that point it calls lock() in the shell plugin. When input events trigger a wakeup, unlock() in the shell plugin

Screen locking protocol

Hi, here is the screen locking protocol patch set for review. It does not actually implement locking yet, only the protocol and hooks intended for it. To test, run the compositor with WAYLAND_DEBUG=1 to see the protocol and -i 5 to have the idle timeout as 5 seconds. Just before sending I notice

RE: Patch for updating gtk over wayland interface

Thanks for your suggestions. Refined the patch, filed a bug for it and send the v2 version.:) - *^_^* BRs, Juan > -Original Message- > From: wayland-devel-bounces+juan.j.zhao=intel@lists.freedesktop.org > [mailto:wayland-devel-bounces+juan.j.zhao=intel@lists.freedesktop.org]

[gtk-wayland v2 PATCH 3/3] ignore the windows updates with wrong width and height

From: Juan Zhao When running applications over wayland, like testcombo. We meet segment fault according to the wrong width and height. Ignore these window's updates. https://bugzilla.gnome.org/show_bug.cgi?id=663550 --- gdk/gdkwindow.c |3 +++ 1 files changed, 3 insertions(+), 0 deletions(-

[gtk-wayland v2 PATCH 2/3] gtk-wayland: update interfaces bindings and display sync APIs

From: Juan Zhao The code can not be compiled, because the wl_display related interfaces are changed in wayland. Update wl_display_sync_callback APIs to wl_callback_add_listener and wl_display_roundtrip for display sync. Because wl_xxx_create is removed in wayland. Update it to wl_display_bind f

[gtk-wayland v2 PATCH 1/3] update wl_visual related operations to eglconfig

From: Juan Zhao Because wl_visual related interfaces are removed in wayland, the code can not be compiled. We should replace them by the use of egl configs or shm format tokens. We also need to certificate the eglconfig before creating the egl context. Use environment parameter GTK_WAYLAN_PRE

Re: [PATCH] compositor: pass options to the shell process, v2

On 11/07/2011 11:06 AM, Pekka Paalanen wrote: When desktop-shell was changed to be launched by the compositor alone, we also lost the opportunity to give it arguments, specifically the background picture. Add the compositor option -b (--shell-options) for passing arguments to the shell process.

[PATCH] compositor: pass options to the shell process, v2

When desktop-shell was changed to be launched by the compositor alone, we also lost the opportunity to give it arguments, specifically the background picture. Add the compositor option -b (--shell-options) for passing arguments to the shell process. The parameter to -b is a comma-separated list of