[PATCH] compositor: Damage output when restoring X window.
Kristian Høgsberg
krh at bitplanet.net
Fri Jan 27 08:32:05 PST 2012
On Fri, Jan 27, 2012 at 5:39 AM, Scott Moreau <oreaus at gmail.com> wrote:
When do you see the damage? Are you not using a compositing window
manager? We probably need to do x11_compositor_find_output and then
weston_output_damage in the XCB_EXPOSE: case instead.
Kristian
> src/compositor-x11.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/src/compositor-x11.c b/src/compositor-x11.c
> index 09213f7..3afd6fa 100644
> --- a/src/compositor-x11.c
> +++ b/src/compositor-x11.c
> @@ -599,6 +599,8 @@ x11_compositor_handle_event(int fd, uint32_t mask, void *data)
> weston_compositor_get_time(),
> &output->base, &c->keys);
>
> + weston_output_damage((struct weston_output *) output);
> +
> free(prev);
> prev = NULL;
> break;
> --
> 1.7.4.1
>
> _______________________________________________
> wayland-devel mailing list
> wayland-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/wayland-devel
More information about the wayland-devel
mailing list