window-actor: Split into two subclasses of MetaSurfaceActor
The rendering logic before was somewhat complex. We had three independent
cases to take into account when doing rendering:
* X11 compositor. In this case, we're a traditional X11 compositor,
not a Wayland compositor. We use XCompositeNameWindowPixmap to get
the backing pixmap for the window, and deal with the COMPOSITE
extension messiness.
In this case, meta_is_wayland_compositor() is FALSE.
* Wayland clients. In this case, we're a Wayland compositor managing
Wayland surfaces. The rendering for this is fairly straightforward,
as Cogl handles most of the complexity with EGL and SHM buffers...
Wayland clients give us the input and opaque regions through
wl_surface.
In this case, meta_is_wayland_compositor() is TRUE and
priv->window->client_type == META_WINDOW_CLIENT_TYPE_WAYLAND.
* XWayland clients. In this case, we're a Wayland compositor, like
above, and XWayland hands us Wayland surfaces. XWayland handles
the COMPOSITE extension messiness for us, and hands us a buffer
like any other Wayland client. We have to fetch the input and
opaque regions from the X11 window ourselves.
In this case, meta_is_wayland_compositor() is TRUE and
priv->window->client_type == META_WINDOW_CLIENT_TYPE_X11.
We now split the rendering logic into two subclasses, which are:
* MetaSurfaceActorX11, which handles the X11 compositor case, in that
it uses XCompositeNameWindowPixmap to get the backing pixmap, and
deal with all the COMPOSITE extension messiness.
* MetaSurfaceActorWayland, which handles the Wayland compositor case
for both native Wayland clients and XWayland clients. XWayland handles
COMPOSITE for us, and handles pushing a surface over through the
xf86-video-wayland DDX.
Frame sync is still in MetaWindowActor, as it needs to work for both the
X11 compositor and XWayland client cases. When Wayland's video display
protocol lands, this will need to be significantly overhauled, as it would
have to work for any wl_surface, including subsurfaces, so we would need
surface-level discretion.
https://bugzilla.gnome.org/show_bug.cgi?id=720631
2014-02-01 17:21:11 -05:00
|
|
|
/* -*- mode: C; c-file-style: "gnu"; indent-tabs-mode: nil; -*- */
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Copyright (C) 2013 Red Hat
|
|
|
|
*
|
|
|
|
* This program is free software; you can redistribute it and/or
|
|
|
|
* modify it under the terms of the GNU General Public License as
|
|
|
|
* published by the Free Software Foundation; either version 2 of the
|
|
|
|
* License, or (at your option) any later version.
|
|
|
|
*
|
|
|
|
* This program is distributed in the hope that it will be useful, but
|
|
|
|
* WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
|
|
|
|
* General Public License for more details.
|
|
|
|
*
|
|
|
|
* You should have received a copy of the GNU General Public License
|
|
|
|
* along with this program; if not, write to the Free Software
|
|
|
|
* Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA
|
|
|
|
* 02111-1307, USA.
|
|
|
|
*
|
|
|
|
* Written by:
|
|
|
|
* Owen Taylor <otaylor@redhat.com>
|
|
|
|
* Jasper St. Pierre <jstpierre@mecheye.net>
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include "config.h"
|
|
|
|
|
|
|
|
#include "meta-surface-actor-x11.h"
|
|
|
|
|
|
|
|
#include <X11/extensions/Xcomposite.h>
|
|
|
|
#include <cogl/cogl-texture-pixmap-x11.h>
|
|
|
|
|
|
|
|
#include <meta/errors.h>
|
|
|
|
#include "window-private.h"
|
|
|
|
#include "meta-shaped-texture-private.h"
|
|
|
|
#include "meta-cullable.h"
|
2014-06-16 18:25:40 -04:00
|
|
|
#include "x11/window-x11.h"
|
window-actor: Split into two subclasses of MetaSurfaceActor
The rendering logic before was somewhat complex. We had three independent
cases to take into account when doing rendering:
* X11 compositor. In this case, we're a traditional X11 compositor,
not a Wayland compositor. We use XCompositeNameWindowPixmap to get
the backing pixmap for the window, and deal with the COMPOSITE
extension messiness.
In this case, meta_is_wayland_compositor() is FALSE.
* Wayland clients. In this case, we're a Wayland compositor managing
Wayland surfaces. The rendering for this is fairly straightforward,
as Cogl handles most of the complexity with EGL and SHM buffers...
Wayland clients give us the input and opaque regions through
wl_surface.
In this case, meta_is_wayland_compositor() is TRUE and
priv->window->client_type == META_WINDOW_CLIENT_TYPE_WAYLAND.
* XWayland clients. In this case, we're a Wayland compositor, like
above, and XWayland hands us Wayland surfaces. XWayland handles
the COMPOSITE extension messiness for us, and hands us a buffer
like any other Wayland client. We have to fetch the input and
opaque regions from the X11 window ourselves.
In this case, meta_is_wayland_compositor() is TRUE and
priv->window->client_type == META_WINDOW_CLIENT_TYPE_X11.
We now split the rendering logic into two subclasses, which are:
* MetaSurfaceActorX11, which handles the X11 compositor case, in that
it uses XCompositeNameWindowPixmap to get the backing pixmap, and
deal with all the COMPOSITE extension messiness.
* MetaSurfaceActorWayland, which handles the Wayland compositor case
for both native Wayland clients and XWayland clients. XWayland handles
COMPOSITE for us, and handles pushing a surface over through the
xf86-video-wayland DDX.
Frame sync is still in MetaWindowActor, as it needs to work for both the
X11 compositor and XWayland client cases. When Wayland's video display
protocol lands, this will need to be significantly overhauled, as it would
have to work for any wl_surface, including subsurfaces, so we would need
surface-level discretion.
https://bugzilla.gnome.org/show_bug.cgi?id=720631
2014-02-01 17:21:11 -05:00
|
|
|
|
|
|
|
struct _MetaSurfaceActorX11Private
|
|
|
|
{
|
|
|
|
MetaWindow *window;
|
|
|
|
|
|
|
|
MetaDisplay *display;
|
|
|
|
|
|
|
|
CoglTexture *texture;
|
|
|
|
Pixmap pixmap;
|
|
|
|
Damage damage;
|
|
|
|
|
|
|
|
int last_width;
|
|
|
|
int last_height;
|
|
|
|
|
|
|
|
/* This is used to detect fullscreen windows that need to be unredirected */
|
|
|
|
guint full_damage_frames_count;
|
|
|
|
guint does_full_damage : 1;
|
|
|
|
|
|
|
|
/* Other state... */
|
|
|
|
guint received_damage : 1;
|
|
|
|
guint size_changed : 1;
|
|
|
|
|
|
|
|
guint unredirected : 1;
|
|
|
|
};
|
|
|
|
typedef struct _MetaSurfaceActorX11Private MetaSurfaceActorX11Private;
|
|
|
|
|
|
|
|
G_DEFINE_TYPE_WITH_PRIVATE (MetaSurfaceActorX11, meta_surface_actor_x11, META_TYPE_SURFACE_ACTOR)
|
|
|
|
|
|
|
|
static void
|
|
|
|
free_damage (MetaSurfaceActorX11 *self)
|
|
|
|
{
|
|
|
|
MetaSurfaceActorX11Private *priv = meta_surface_actor_x11_get_instance_private (self);
|
|
|
|
MetaDisplay *display = priv->display;
|
|
|
|
Display *xdisplay = meta_display_get_xdisplay (display);
|
|
|
|
|
|
|
|
if (priv->damage == None)
|
|
|
|
return;
|
|
|
|
|
|
|
|
meta_error_trap_push (display);
|
|
|
|
XDamageDestroy (xdisplay, priv->damage);
|
|
|
|
priv->damage = None;
|
|
|
|
meta_error_trap_pop (display);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
detach_pixmap (MetaSurfaceActorX11 *self)
|
|
|
|
{
|
|
|
|
MetaSurfaceActorX11Private *priv = meta_surface_actor_x11_get_instance_private (self);
|
|
|
|
MetaDisplay *display = priv->display;
|
|
|
|
Display *xdisplay = meta_display_get_xdisplay (display);
|
|
|
|
MetaShapedTexture *stex = meta_surface_actor_get_texture (META_SURFACE_ACTOR (self));
|
|
|
|
|
|
|
|
if (priv->pixmap == None)
|
|
|
|
return;
|
|
|
|
|
|
|
|
/* Get rid of all references to the pixmap before freeing it; it's unclear whether
|
|
|
|
* you are supposed to be able to free a GLXPixmap after freeing the underlying
|
|
|
|
* pixmap, but it certainly doesn't work with current DRI/Mesa
|
|
|
|
*/
|
|
|
|
meta_shaped_texture_set_texture (stex, NULL);
|
|
|
|
cogl_flush ();
|
|
|
|
|
|
|
|
meta_error_trap_push (display);
|
|
|
|
XFreePixmap (xdisplay, priv->pixmap);
|
|
|
|
priv->pixmap = None;
|
|
|
|
meta_error_trap_pop (display);
|
|
|
|
|
|
|
|
cogl_object_unref (priv->texture);
|
|
|
|
priv->texture = NULL;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
set_pixmap (MetaSurfaceActorX11 *self,
|
|
|
|
Pixmap pixmap)
|
|
|
|
{
|
|
|
|
MetaSurfaceActorX11Private *priv = meta_surface_actor_x11_get_instance_private (self);
|
|
|
|
|
|
|
|
CoglContext *ctx = clutter_backend_get_cogl_context (clutter_get_default_backend ());
|
|
|
|
MetaShapedTexture *stex = meta_surface_actor_get_texture (META_SURFACE_ACTOR (self));
|
|
|
|
CoglTexture *texture;
|
|
|
|
|
|
|
|
g_assert (priv->pixmap == None);
|
|
|
|
priv->pixmap = pixmap;
|
|
|
|
|
|
|
|
texture = COGL_TEXTURE (cogl_texture_pixmap_x11_new (ctx, priv->pixmap, FALSE, NULL));
|
|
|
|
|
|
|
|
if (G_UNLIKELY (!cogl_texture_pixmap_x11_is_using_tfp_extension (COGL_TEXTURE_PIXMAP_X11 (texture))))
|
|
|
|
g_warning ("NOTE: Not using GLX TFP!\n");
|
|
|
|
|
|
|
|
priv->texture = texture;
|
|
|
|
meta_shaped_texture_set_texture (stex, texture);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
update_pixmap (MetaSurfaceActorX11 *self)
|
|
|
|
{
|
|
|
|
MetaSurfaceActorX11Private *priv = meta_surface_actor_x11_get_instance_private (self);
|
|
|
|
MetaDisplay *display = priv->display;
|
|
|
|
Display *xdisplay = meta_display_get_xdisplay (display);
|
|
|
|
|
|
|
|
if (priv->size_changed)
|
|
|
|
{
|
|
|
|
detach_pixmap (self);
|
|
|
|
priv->size_changed = FALSE;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (priv->pixmap == None)
|
|
|
|
{
|
|
|
|
Pixmap new_pixmap;
|
2014-06-16 18:25:40 -04:00
|
|
|
Window xwindow = meta_window_x11_get_toplevel_xwindow (priv->window);
|
window-actor: Split into two subclasses of MetaSurfaceActor
The rendering logic before was somewhat complex. We had three independent
cases to take into account when doing rendering:
* X11 compositor. In this case, we're a traditional X11 compositor,
not a Wayland compositor. We use XCompositeNameWindowPixmap to get
the backing pixmap for the window, and deal with the COMPOSITE
extension messiness.
In this case, meta_is_wayland_compositor() is FALSE.
* Wayland clients. In this case, we're a Wayland compositor managing
Wayland surfaces. The rendering for this is fairly straightforward,
as Cogl handles most of the complexity with EGL and SHM buffers...
Wayland clients give us the input and opaque regions through
wl_surface.
In this case, meta_is_wayland_compositor() is TRUE and
priv->window->client_type == META_WINDOW_CLIENT_TYPE_WAYLAND.
* XWayland clients. In this case, we're a Wayland compositor, like
above, and XWayland hands us Wayland surfaces. XWayland handles
the COMPOSITE extension messiness for us, and hands us a buffer
like any other Wayland client. We have to fetch the input and
opaque regions from the X11 window ourselves.
In this case, meta_is_wayland_compositor() is TRUE and
priv->window->client_type == META_WINDOW_CLIENT_TYPE_X11.
We now split the rendering logic into two subclasses, which are:
* MetaSurfaceActorX11, which handles the X11 compositor case, in that
it uses XCompositeNameWindowPixmap to get the backing pixmap, and
deal with all the COMPOSITE extension messiness.
* MetaSurfaceActorWayland, which handles the Wayland compositor case
for both native Wayland clients and XWayland clients. XWayland handles
COMPOSITE for us, and handles pushing a surface over through the
xf86-video-wayland DDX.
Frame sync is still in MetaWindowActor, as it needs to work for both the
X11 compositor and XWayland client cases. When Wayland's video display
protocol lands, this will need to be significantly overhauled, as it would
have to work for any wl_surface, including subsurfaces, so we would need
surface-level discretion.
https://bugzilla.gnome.org/show_bug.cgi?id=720631
2014-02-01 17:21:11 -05:00
|
|
|
|
|
|
|
meta_error_trap_push (display);
|
|
|
|
new_pixmap = XCompositeNameWindowPixmap (xdisplay, xwindow);
|
|
|
|
|
|
|
|
if (meta_error_trap_pop_with_return (display) != Success)
|
|
|
|
{
|
|
|
|
/* Probably a BadMatch if the window isn't viewable; we could
|
|
|
|
* GrabServer/GetWindowAttributes/NameWindowPixmap/UngrabServer/Sync
|
|
|
|
* to avoid this, but there's no reason to take two round trips
|
|
|
|
* when one will do. (We need that Sync if we want to handle failures
|
|
|
|
* for any reason other than !viewable. That's unlikely, but maybe
|
|
|
|
* we'll BadAlloc or something.)
|
|
|
|
*/
|
|
|
|
new_pixmap = None;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (new_pixmap == None)
|
|
|
|
{
|
|
|
|
meta_verbose ("Unable to get named pixmap for %s\n",
|
|
|
|
meta_window_get_description (priv->window));
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
set_pixmap (self, new_pixmap);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
static gboolean
|
|
|
|
is_visible (MetaSurfaceActorX11 *self)
|
|
|
|
{
|
|
|
|
MetaSurfaceActorX11Private *priv = meta_surface_actor_x11_get_instance_private (self);
|
|
|
|
return (priv->pixmap != None) && !priv->unredirected;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
meta_surface_actor_x11_process_damage (MetaSurfaceActor *actor,
|
|
|
|
int x, int y, int width, int height)
|
|
|
|
{
|
|
|
|
MetaSurfaceActorX11 *self = META_SURFACE_ACTOR_X11 (actor);
|
|
|
|
MetaSurfaceActorX11Private *priv = meta_surface_actor_x11_get_instance_private (self);
|
|
|
|
|
|
|
|
priv->received_damage = TRUE;
|
|
|
|
|
|
|
|
if (meta_window_is_fullscreen (priv->window) && !priv->unredirected && !priv->does_full_damage)
|
|
|
|
{
|
|
|
|
MetaRectangle window_rect;
|
|
|
|
meta_window_get_frame_rect (priv->window, &window_rect);
|
|
|
|
|
|
|
|
if (window_rect.x == x &&
|
|
|
|
window_rect.y == y &&
|
|
|
|
window_rect.width == width &&
|
|
|
|
window_rect.height == height)
|
|
|
|
priv->full_damage_frames_count++;
|
|
|
|
else
|
|
|
|
priv->full_damage_frames_count = 0;
|
|
|
|
|
|
|
|
if (priv->full_damage_frames_count >= 100)
|
|
|
|
priv->does_full_damage = TRUE;
|
|
|
|
}
|
|
|
|
|
2014-08-21 18:30:35 -04:00
|
|
|
if (!is_visible (actor))
|
window-actor: Split into two subclasses of MetaSurfaceActor
The rendering logic before was somewhat complex. We had three independent
cases to take into account when doing rendering:
* X11 compositor. In this case, we're a traditional X11 compositor,
not a Wayland compositor. We use XCompositeNameWindowPixmap to get
the backing pixmap for the window, and deal with the COMPOSITE
extension messiness.
In this case, meta_is_wayland_compositor() is FALSE.
* Wayland clients. In this case, we're a Wayland compositor managing
Wayland surfaces. The rendering for this is fairly straightforward,
as Cogl handles most of the complexity with EGL and SHM buffers...
Wayland clients give us the input and opaque regions through
wl_surface.
In this case, meta_is_wayland_compositor() is TRUE and
priv->window->client_type == META_WINDOW_CLIENT_TYPE_WAYLAND.
* XWayland clients. In this case, we're a Wayland compositor, like
above, and XWayland hands us Wayland surfaces. XWayland handles
the COMPOSITE extension messiness for us, and hands us a buffer
like any other Wayland client. We have to fetch the input and
opaque regions from the X11 window ourselves.
In this case, meta_is_wayland_compositor() is TRUE and
priv->window->client_type == META_WINDOW_CLIENT_TYPE_X11.
We now split the rendering logic into two subclasses, which are:
* MetaSurfaceActorX11, which handles the X11 compositor case, in that
it uses XCompositeNameWindowPixmap to get the backing pixmap, and
deal with all the COMPOSITE extension messiness.
* MetaSurfaceActorWayland, which handles the Wayland compositor case
for both native Wayland clients and XWayland clients. XWayland handles
COMPOSITE for us, and handles pushing a surface over through the
xf86-video-wayland DDX.
Frame sync is still in MetaWindowActor, as it needs to work for both the
X11 compositor and XWayland client cases. When Wayland's video display
protocol lands, this will need to be significantly overhauled, as it would
have to work for any wl_surface, including subsurfaces, so we would need
surface-level discretion.
https://bugzilla.gnome.org/show_bug.cgi?id=720631
2014-02-01 17:21:11 -05:00
|
|
|
return;
|
|
|
|
|
2014-08-21 18:30:17 -04:00
|
|
|
cogl_texture_pixmap_x11_update_area (priv->texture, x, y, width, height);
|
window-actor: Split into two subclasses of MetaSurfaceActor
The rendering logic before was somewhat complex. We had three independent
cases to take into account when doing rendering:
* X11 compositor. In this case, we're a traditional X11 compositor,
not a Wayland compositor. We use XCompositeNameWindowPixmap to get
the backing pixmap for the window, and deal with the COMPOSITE
extension messiness.
In this case, meta_is_wayland_compositor() is FALSE.
* Wayland clients. In this case, we're a Wayland compositor managing
Wayland surfaces. The rendering for this is fairly straightforward,
as Cogl handles most of the complexity with EGL and SHM buffers...
Wayland clients give us the input and opaque regions through
wl_surface.
In this case, meta_is_wayland_compositor() is TRUE and
priv->window->client_type == META_WINDOW_CLIENT_TYPE_WAYLAND.
* XWayland clients. In this case, we're a Wayland compositor, like
above, and XWayland hands us Wayland surfaces. XWayland handles
the COMPOSITE extension messiness for us, and hands us a buffer
like any other Wayland client. We have to fetch the input and
opaque regions from the X11 window ourselves.
In this case, meta_is_wayland_compositor() is TRUE and
priv->window->client_type == META_WINDOW_CLIENT_TYPE_X11.
We now split the rendering logic into two subclasses, which are:
* MetaSurfaceActorX11, which handles the X11 compositor case, in that
it uses XCompositeNameWindowPixmap to get the backing pixmap, and
deal with all the COMPOSITE extension messiness.
* MetaSurfaceActorWayland, which handles the Wayland compositor case
for both native Wayland clients and XWayland clients. XWayland handles
COMPOSITE for us, and handles pushing a surface over through the
xf86-video-wayland DDX.
Frame sync is still in MetaWindowActor, as it needs to work for both the
X11 compositor and XWayland client cases. When Wayland's video display
protocol lands, this will need to be significantly overhauled, as it would
have to work for any wl_surface, including subsurfaces, so we would need
surface-level discretion.
https://bugzilla.gnome.org/show_bug.cgi?id=720631
2014-02-01 17:21:11 -05:00
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
meta_surface_actor_x11_pre_paint (MetaSurfaceActor *actor)
|
|
|
|
{
|
|
|
|
MetaSurfaceActorX11 *self = META_SURFACE_ACTOR_X11 (actor);
|
|
|
|
MetaSurfaceActorX11Private *priv = meta_surface_actor_x11_get_instance_private (self);
|
|
|
|
MetaDisplay *display = priv->display;
|
|
|
|
Display *xdisplay = meta_display_get_xdisplay (display);
|
|
|
|
|
|
|
|
if (priv->received_damage)
|
|
|
|
{
|
|
|
|
meta_error_trap_push (display);
|
|
|
|
XDamageSubtract (xdisplay, priv->damage, None, None);
|
|
|
|
meta_error_trap_pop (display);
|
|
|
|
|
|
|
|
priv->received_damage = FALSE;
|
|
|
|
}
|
|
|
|
|
|
|
|
update_pixmap (self);
|
|
|
|
}
|
|
|
|
|
|
|
|
static gboolean
|
|
|
|
meta_surface_actor_x11_is_visible (MetaSurfaceActor *actor)
|
|
|
|
{
|
|
|
|
MetaSurfaceActorX11 *self = META_SURFACE_ACTOR_X11 (actor);
|
|
|
|
return is_visible (self);
|
|
|
|
}
|
|
|
|
|
|
|
|
static gboolean
|
|
|
|
meta_surface_actor_x11_should_unredirect (MetaSurfaceActor *actor)
|
|
|
|
{
|
|
|
|
MetaSurfaceActorX11 *self = META_SURFACE_ACTOR_X11 (actor);
|
|
|
|
MetaSurfaceActorX11Private *priv = meta_surface_actor_x11_get_instance_private (self);
|
|
|
|
|
|
|
|
MetaWindow *window = priv->window;
|
|
|
|
|
|
|
|
if (meta_window_requested_dont_bypass_compositor (window))
|
|
|
|
return FALSE;
|
|
|
|
|
|
|
|
if (window->opacity != 0xFF)
|
|
|
|
return FALSE;
|
|
|
|
|
|
|
|
if (window->shape_region != NULL)
|
|
|
|
return FALSE;
|
|
|
|
|
2014-03-25 17:02:50 -04:00
|
|
|
if (meta_surface_actor_is_argb32 (actor) && !meta_window_requested_bypass_compositor (window))
|
window-actor: Split into two subclasses of MetaSurfaceActor
The rendering logic before was somewhat complex. We had three independent
cases to take into account when doing rendering:
* X11 compositor. In this case, we're a traditional X11 compositor,
not a Wayland compositor. We use XCompositeNameWindowPixmap to get
the backing pixmap for the window, and deal with the COMPOSITE
extension messiness.
In this case, meta_is_wayland_compositor() is FALSE.
* Wayland clients. In this case, we're a Wayland compositor managing
Wayland surfaces. The rendering for this is fairly straightforward,
as Cogl handles most of the complexity with EGL and SHM buffers...
Wayland clients give us the input and opaque regions through
wl_surface.
In this case, meta_is_wayland_compositor() is TRUE and
priv->window->client_type == META_WINDOW_CLIENT_TYPE_WAYLAND.
* XWayland clients. In this case, we're a Wayland compositor, like
above, and XWayland hands us Wayland surfaces. XWayland handles
the COMPOSITE extension messiness for us, and hands us a buffer
like any other Wayland client. We have to fetch the input and
opaque regions from the X11 window ourselves.
In this case, meta_is_wayland_compositor() is TRUE and
priv->window->client_type == META_WINDOW_CLIENT_TYPE_X11.
We now split the rendering logic into two subclasses, which are:
* MetaSurfaceActorX11, which handles the X11 compositor case, in that
it uses XCompositeNameWindowPixmap to get the backing pixmap, and
deal with all the COMPOSITE extension messiness.
* MetaSurfaceActorWayland, which handles the Wayland compositor case
for both native Wayland clients and XWayland clients. XWayland handles
COMPOSITE for us, and handles pushing a surface over through the
xf86-video-wayland DDX.
Frame sync is still in MetaWindowActor, as it needs to work for both the
X11 compositor and XWayland client cases. When Wayland's video display
protocol lands, this will need to be significantly overhauled, as it would
have to work for any wl_surface, including subsurfaces, so we would need
surface-level discretion.
https://bugzilla.gnome.org/show_bug.cgi?id=720631
2014-02-01 17:21:11 -05:00
|
|
|
return FALSE;
|
|
|
|
|
|
|
|
if (!meta_window_is_monitor_sized (window))
|
|
|
|
return FALSE;
|
|
|
|
|
|
|
|
if (meta_window_requested_bypass_compositor (window))
|
|
|
|
return TRUE;
|
|
|
|
|
|
|
|
if (meta_window_is_override_redirect (window))
|
|
|
|
return TRUE;
|
|
|
|
|
|
|
|
if (priv->does_full_damage)
|
|
|
|
return TRUE;
|
|
|
|
|
|
|
|
return FALSE;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
sync_unredirected (MetaSurfaceActorX11 *self)
|
|
|
|
{
|
|
|
|
MetaSurfaceActorX11Private *priv = meta_surface_actor_x11_get_instance_private (self);
|
|
|
|
MetaDisplay *display = priv->display;
|
|
|
|
Display *xdisplay = meta_display_get_xdisplay (display);
|
2014-06-16 18:25:40 -04:00
|
|
|
Window xwindow = meta_window_x11_get_toplevel_xwindow (priv->window);
|
window-actor: Split into two subclasses of MetaSurfaceActor
The rendering logic before was somewhat complex. We had three independent
cases to take into account when doing rendering:
* X11 compositor. In this case, we're a traditional X11 compositor,
not a Wayland compositor. We use XCompositeNameWindowPixmap to get
the backing pixmap for the window, and deal with the COMPOSITE
extension messiness.
In this case, meta_is_wayland_compositor() is FALSE.
* Wayland clients. In this case, we're a Wayland compositor managing
Wayland surfaces. The rendering for this is fairly straightforward,
as Cogl handles most of the complexity with EGL and SHM buffers...
Wayland clients give us the input and opaque regions through
wl_surface.
In this case, meta_is_wayland_compositor() is TRUE and
priv->window->client_type == META_WINDOW_CLIENT_TYPE_WAYLAND.
* XWayland clients. In this case, we're a Wayland compositor, like
above, and XWayland hands us Wayland surfaces. XWayland handles
the COMPOSITE extension messiness for us, and hands us a buffer
like any other Wayland client. We have to fetch the input and
opaque regions from the X11 window ourselves.
In this case, meta_is_wayland_compositor() is TRUE and
priv->window->client_type == META_WINDOW_CLIENT_TYPE_X11.
We now split the rendering logic into two subclasses, which are:
* MetaSurfaceActorX11, which handles the X11 compositor case, in that
it uses XCompositeNameWindowPixmap to get the backing pixmap, and
deal with all the COMPOSITE extension messiness.
* MetaSurfaceActorWayland, which handles the Wayland compositor case
for both native Wayland clients and XWayland clients. XWayland handles
COMPOSITE for us, and handles pushing a surface over through the
xf86-video-wayland DDX.
Frame sync is still in MetaWindowActor, as it needs to work for both the
X11 compositor and XWayland client cases. When Wayland's video display
protocol lands, this will need to be significantly overhauled, as it would
have to work for any wl_surface, including subsurfaces, so we would need
surface-level discretion.
https://bugzilla.gnome.org/show_bug.cgi?id=720631
2014-02-01 17:21:11 -05:00
|
|
|
|
|
|
|
meta_error_trap_push (display);
|
|
|
|
|
|
|
|
if (priv->unredirected)
|
|
|
|
{
|
|
|
|
detach_pixmap (self);
|
|
|
|
XCompositeUnredirectWindow (xdisplay, xwindow, CompositeRedirectManual);
|
|
|
|
}
|
|
|
|
else
|
|
|
|
{
|
|
|
|
XCompositeRedirectWindow (xdisplay, xwindow, CompositeRedirectManual);
|
|
|
|
}
|
|
|
|
|
|
|
|
meta_error_trap_pop (display);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
meta_surface_actor_x11_set_unredirected (MetaSurfaceActor *actor,
|
|
|
|
gboolean unredirected)
|
|
|
|
{
|
|
|
|
MetaSurfaceActorX11 *self = META_SURFACE_ACTOR_X11 (actor);
|
|
|
|
MetaSurfaceActorX11Private *priv = meta_surface_actor_x11_get_instance_private (self);
|
|
|
|
|
|
|
|
if (priv->unredirected == unredirected)
|
|
|
|
return;
|
|
|
|
|
|
|
|
priv->unredirected = unredirected;
|
|
|
|
sync_unredirected (self);
|
|
|
|
}
|
|
|
|
|
|
|
|
static gboolean
|
|
|
|
meta_surface_actor_x11_is_unredirected (MetaSurfaceActor *actor)
|
|
|
|
{
|
|
|
|
MetaSurfaceActorX11 *self = META_SURFACE_ACTOR_X11 (actor);
|
|
|
|
MetaSurfaceActorX11Private *priv = meta_surface_actor_x11_get_instance_private (self);
|
|
|
|
|
|
|
|
return priv->unredirected;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
meta_surface_actor_x11_dispose (GObject *object)
|
|
|
|
{
|
|
|
|
MetaSurfaceActorX11 *self = META_SURFACE_ACTOR_X11 (object);
|
|
|
|
|
|
|
|
detach_pixmap (self);
|
|
|
|
free_damage (self);
|
|
|
|
|
|
|
|
G_OBJECT_CLASS (meta_surface_actor_x11_parent_class)->dispose (object);
|
|
|
|
}
|
|
|
|
|
2014-02-26 20:21:51 -05:00
|
|
|
static MetaWindow *
|
|
|
|
meta_surface_actor_x11_get_window (MetaSurfaceActor *actor)
|
|
|
|
{
|
|
|
|
MetaSurfaceActorX11Private *priv = meta_surface_actor_x11_get_instance_private (META_SURFACE_ACTOR_X11 (actor));
|
|
|
|
|
|
|
|
return priv->window;
|
|
|
|
}
|
|
|
|
|
window-actor: Split into two subclasses of MetaSurfaceActor
The rendering logic before was somewhat complex. We had three independent
cases to take into account when doing rendering:
* X11 compositor. In this case, we're a traditional X11 compositor,
not a Wayland compositor. We use XCompositeNameWindowPixmap to get
the backing pixmap for the window, and deal with the COMPOSITE
extension messiness.
In this case, meta_is_wayland_compositor() is FALSE.
* Wayland clients. In this case, we're a Wayland compositor managing
Wayland surfaces. The rendering for this is fairly straightforward,
as Cogl handles most of the complexity with EGL and SHM buffers...
Wayland clients give us the input and opaque regions through
wl_surface.
In this case, meta_is_wayland_compositor() is TRUE and
priv->window->client_type == META_WINDOW_CLIENT_TYPE_WAYLAND.
* XWayland clients. In this case, we're a Wayland compositor, like
above, and XWayland hands us Wayland surfaces. XWayland handles
the COMPOSITE extension messiness for us, and hands us a buffer
like any other Wayland client. We have to fetch the input and
opaque regions from the X11 window ourselves.
In this case, meta_is_wayland_compositor() is TRUE and
priv->window->client_type == META_WINDOW_CLIENT_TYPE_X11.
We now split the rendering logic into two subclasses, which are:
* MetaSurfaceActorX11, which handles the X11 compositor case, in that
it uses XCompositeNameWindowPixmap to get the backing pixmap, and
deal with all the COMPOSITE extension messiness.
* MetaSurfaceActorWayland, which handles the Wayland compositor case
for both native Wayland clients and XWayland clients. XWayland handles
COMPOSITE for us, and handles pushing a surface over through the
xf86-video-wayland DDX.
Frame sync is still in MetaWindowActor, as it needs to work for both the
X11 compositor and XWayland client cases. When Wayland's video display
protocol lands, this will need to be significantly overhauled, as it would
have to work for any wl_surface, including subsurfaces, so we would need
surface-level discretion.
https://bugzilla.gnome.org/show_bug.cgi?id=720631
2014-02-01 17:21:11 -05:00
|
|
|
static void
|
|
|
|
meta_surface_actor_x11_class_init (MetaSurfaceActorX11Class *klass)
|
|
|
|
{
|
|
|
|
GObjectClass *object_class = G_OBJECT_CLASS (klass);
|
|
|
|
MetaSurfaceActorClass *surface_actor_class = META_SURFACE_ACTOR_CLASS (klass);
|
|
|
|
|
|
|
|
object_class->dispose = meta_surface_actor_x11_dispose;
|
|
|
|
|
|
|
|
surface_actor_class->process_damage = meta_surface_actor_x11_process_damage;
|
|
|
|
surface_actor_class->pre_paint = meta_surface_actor_x11_pre_paint;
|
|
|
|
surface_actor_class->is_visible = meta_surface_actor_x11_is_visible;
|
|
|
|
|
|
|
|
surface_actor_class->should_unredirect = meta_surface_actor_x11_should_unredirect;
|
|
|
|
surface_actor_class->set_unredirected = meta_surface_actor_x11_set_unredirected;
|
|
|
|
surface_actor_class->is_unredirected = meta_surface_actor_x11_is_unredirected;
|
2014-02-26 20:21:51 -05:00
|
|
|
|
|
|
|
surface_actor_class->get_window = meta_surface_actor_x11_get_window;
|
window-actor: Split into two subclasses of MetaSurfaceActor
The rendering logic before was somewhat complex. We had three independent
cases to take into account when doing rendering:
* X11 compositor. In this case, we're a traditional X11 compositor,
not a Wayland compositor. We use XCompositeNameWindowPixmap to get
the backing pixmap for the window, and deal with the COMPOSITE
extension messiness.
In this case, meta_is_wayland_compositor() is FALSE.
* Wayland clients. In this case, we're a Wayland compositor managing
Wayland surfaces. The rendering for this is fairly straightforward,
as Cogl handles most of the complexity with EGL and SHM buffers...
Wayland clients give us the input and opaque regions through
wl_surface.
In this case, meta_is_wayland_compositor() is TRUE and
priv->window->client_type == META_WINDOW_CLIENT_TYPE_WAYLAND.
* XWayland clients. In this case, we're a Wayland compositor, like
above, and XWayland hands us Wayland surfaces. XWayland handles
the COMPOSITE extension messiness for us, and hands us a buffer
like any other Wayland client. We have to fetch the input and
opaque regions from the X11 window ourselves.
In this case, meta_is_wayland_compositor() is TRUE and
priv->window->client_type == META_WINDOW_CLIENT_TYPE_X11.
We now split the rendering logic into two subclasses, which are:
* MetaSurfaceActorX11, which handles the X11 compositor case, in that
it uses XCompositeNameWindowPixmap to get the backing pixmap, and
deal with all the COMPOSITE extension messiness.
* MetaSurfaceActorWayland, which handles the Wayland compositor case
for both native Wayland clients and XWayland clients. XWayland handles
COMPOSITE for us, and handles pushing a surface over through the
xf86-video-wayland DDX.
Frame sync is still in MetaWindowActor, as it needs to work for both the
X11 compositor and XWayland client cases. When Wayland's video display
protocol lands, this will need to be significantly overhauled, as it would
have to work for any wl_surface, including subsurfaces, so we would need
surface-level discretion.
https://bugzilla.gnome.org/show_bug.cgi?id=720631
2014-02-01 17:21:11 -05:00
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
meta_surface_actor_x11_init (MetaSurfaceActorX11 *self)
|
|
|
|
{
|
|
|
|
MetaSurfaceActorX11Private *priv = meta_surface_actor_x11_get_instance_private (self);
|
|
|
|
|
|
|
|
priv->last_width = -1;
|
|
|
|
priv->last_height = -1;
|
|
|
|
}
|
|
|
|
|
2014-02-20 14:49:22 -05:00
|
|
|
static void
|
|
|
|
create_damage (MetaSurfaceActorX11 *self)
|
|
|
|
{
|
|
|
|
MetaSurfaceActorX11Private *priv = meta_surface_actor_x11_get_instance_private (self);
|
|
|
|
Display *xdisplay = meta_display_get_xdisplay (priv->display);
|
2014-06-16 18:25:40 -04:00
|
|
|
Window xwindow = meta_window_x11_get_toplevel_xwindow (priv->window);
|
2014-02-20 14:49:22 -05:00
|
|
|
|
|
|
|
priv->damage = XDamageCreate (xdisplay, xwindow, XDamageReportBoundingBox);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
window_decorated_notify (MetaWindow *window,
|
|
|
|
GParamSpec *pspec,
|
|
|
|
gpointer user_data)
|
|
|
|
{
|
|
|
|
MetaSurfaceActorX11 *self = META_SURFACE_ACTOR_X11 (user_data);
|
|
|
|
|
|
|
|
free_damage (self);
|
|
|
|
create_damage (self);
|
|
|
|
}
|
|
|
|
|
window-actor: Split into two subclasses of MetaSurfaceActor
The rendering logic before was somewhat complex. We had three independent
cases to take into account when doing rendering:
* X11 compositor. In this case, we're a traditional X11 compositor,
not a Wayland compositor. We use XCompositeNameWindowPixmap to get
the backing pixmap for the window, and deal with the COMPOSITE
extension messiness.
In this case, meta_is_wayland_compositor() is FALSE.
* Wayland clients. In this case, we're a Wayland compositor managing
Wayland surfaces. The rendering for this is fairly straightforward,
as Cogl handles most of the complexity with EGL and SHM buffers...
Wayland clients give us the input and opaque regions through
wl_surface.
In this case, meta_is_wayland_compositor() is TRUE and
priv->window->client_type == META_WINDOW_CLIENT_TYPE_WAYLAND.
* XWayland clients. In this case, we're a Wayland compositor, like
above, and XWayland hands us Wayland surfaces. XWayland handles
the COMPOSITE extension messiness for us, and hands us a buffer
like any other Wayland client. We have to fetch the input and
opaque regions from the X11 window ourselves.
In this case, meta_is_wayland_compositor() is TRUE and
priv->window->client_type == META_WINDOW_CLIENT_TYPE_X11.
We now split the rendering logic into two subclasses, which are:
* MetaSurfaceActorX11, which handles the X11 compositor case, in that
it uses XCompositeNameWindowPixmap to get the backing pixmap, and
deal with all the COMPOSITE extension messiness.
* MetaSurfaceActorWayland, which handles the Wayland compositor case
for both native Wayland clients and XWayland clients. XWayland handles
COMPOSITE for us, and handles pushing a surface over through the
xf86-video-wayland DDX.
Frame sync is still in MetaWindowActor, as it needs to work for both the
X11 compositor and XWayland client cases. When Wayland's video display
protocol lands, this will need to be significantly overhauled, as it would
have to work for any wl_surface, including subsurfaces, so we would need
surface-level discretion.
https://bugzilla.gnome.org/show_bug.cgi?id=720631
2014-02-01 17:21:11 -05:00
|
|
|
MetaSurfaceActor *
|
|
|
|
meta_surface_actor_x11_new (MetaWindow *window)
|
|
|
|
{
|
|
|
|
MetaSurfaceActorX11 *self = g_object_new (META_TYPE_SURFACE_ACTOR_X11, NULL);
|
|
|
|
MetaSurfaceActorX11Private *priv = meta_surface_actor_x11_get_instance_private (self);
|
|
|
|
MetaDisplay *display = meta_window_get_display (window);
|
|
|
|
|
|
|
|
g_assert (!meta_is_wayland_compositor ());
|
|
|
|
|
|
|
|
priv->window = window;
|
|
|
|
priv->display = display;
|
|
|
|
|
2014-02-20 14:49:22 -05:00
|
|
|
create_damage (self);
|
|
|
|
g_signal_connect_object (priv->window, "notify::decorated",
|
|
|
|
G_CALLBACK (window_decorated_notify), self, 0);
|
|
|
|
|
window-actor: Split into two subclasses of MetaSurfaceActor
The rendering logic before was somewhat complex. We had three independent
cases to take into account when doing rendering:
* X11 compositor. In this case, we're a traditional X11 compositor,
not a Wayland compositor. We use XCompositeNameWindowPixmap to get
the backing pixmap for the window, and deal with the COMPOSITE
extension messiness.
In this case, meta_is_wayland_compositor() is FALSE.
* Wayland clients. In this case, we're a Wayland compositor managing
Wayland surfaces. The rendering for this is fairly straightforward,
as Cogl handles most of the complexity with EGL and SHM buffers...
Wayland clients give us the input and opaque regions through
wl_surface.
In this case, meta_is_wayland_compositor() is TRUE and
priv->window->client_type == META_WINDOW_CLIENT_TYPE_WAYLAND.
* XWayland clients. In this case, we're a Wayland compositor, like
above, and XWayland hands us Wayland surfaces. XWayland handles
the COMPOSITE extension messiness for us, and hands us a buffer
like any other Wayland client. We have to fetch the input and
opaque regions from the X11 window ourselves.
In this case, meta_is_wayland_compositor() is TRUE and
priv->window->client_type == META_WINDOW_CLIENT_TYPE_X11.
We now split the rendering logic into two subclasses, which are:
* MetaSurfaceActorX11, which handles the X11 compositor case, in that
it uses XCompositeNameWindowPixmap to get the backing pixmap, and
deal with all the COMPOSITE extension messiness.
* MetaSurfaceActorWayland, which handles the Wayland compositor case
for both native Wayland clients and XWayland clients. XWayland handles
COMPOSITE for us, and handles pushing a surface over through the
xf86-video-wayland DDX.
Frame sync is still in MetaWindowActor, as it needs to work for both the
X11 compositor and XWayland client cases. When Wayland's video display
protocol lands, this will need to be significantly overhauled, as it would
have to work for any wl_surface, including subsurfaces, so we would need
surface-level discretion.
https://bugzilla.gnome.org/show_bug.cgi?id=720631
2014-02-01 17:21:11 -05:00
|
|
|
priv->unredirected = FALSE;
|
|
|
|
sync_unredirected (self);
|
|
|
|
|
2014-02-26 17:46:08 -05:00
|
|
|
clutter_actor_set_reactive (CLUTTER_ACTOR (self), TRUE);
|
window-actor: Split into two subclasses of MetaSurfaceActor
The rendering logic before was somewhat complex. We had three independent
cases to take into account when doing rendering:
* X11 compositor. In this case, we're a traditional X11 compositor,
not a Wayland compositor. We use XCompositeNameWindowPixmap to get
the backing pixmap for the window, and deal with the COMPOSITE
extension messiness.
In this case, meta_is_wayland_compositor() is FALSE.
* Wayland clients. In this case, we're a Wayland compositor managing
Wayland surfaces. The rendering for this is fairly straightforward,
as Cogl handles most of the complexity with EGL and SHM buffers...
Wayland clients give us the input and opaque regions through
wl_surface.
In this case, meta_is_wayland_compositor() is TRUE and
priv->window->client_type == META_WINDOW_CLIENT_TYPE_WAYLAND.
* XWayland clients. In this case, we're a Wayland compositor, like
above, and XWayland hands us Wayland surfaces. XWayland handles
the COMPOSITE extension messiness for us, and hands us a buffer
like any other Wayland client. We have to fetch the input and
opaque regions from the X11 window ourselves.
In this case, meta_is_wayland_compositor() is TRUE and
priv->window->client_type == META_WINDOW_CLIENT_TYPE_X11.
We now split the rendering logic into two subclasses, which are:
* MetaSurfaceActorX11, which handles the X11 compositor case, in that
it uses XCompositeNameWindowPixmap to get the backing pixmap, and
deal with all the COMPOSITE extension messiness.
* MetaSurfaceActorWayland, which handles the Wayland compositor case
for both native Wayland clients and XWayland clients. XWayland handles
COMPOSITE for us, and handles pushing a surface over through the
xf86-video-wayland DDX.
Frame sync is still in MetaWindowActor, as it needs to work for both the
X11 compositor and XWayland client cases. When Wayland's video display
protocol lands, this will need to be significantly overhauled, as it would
have to work for any wl_surface, including subsurfaces, so we would need
surface-level discretion.
https://bugzilla.gnome.org/show_bug.cgi?id=720631
2014-02-01 17:21:11 -05:00
|
|
|
return META_SURFACE_ACTOR (self);
|
|
|
|
}
|
|
|
|
|
|
|
|
void
|
|
|
|
meta_surface_actor_x11_set_size (MetaSurfaceActorX11 *self,
|
|
|
|
int width, int height)
|
|
|
|
{
|
|
|
|
MetaSurfaceActorX11Private *priv = meta_surface_actor_x11_get_instance_private (self);
|
|
|
|
|
|
|
|
if (priv->last_width == width &&
|
|
|
|
priv->last_height == height)
|
|
|
|
return;
|
|
|
|
|
|
|
|
priv->size_changed = TRUE;
|
|
|
|
priv->last_width = width;
|
|
|
|
priv->last_height = height;
|
|
|
|
}
|