mutter/src/wayland/meta-window-xwayland.c

222 lines
7.3 KiB
C
Raw Normal View History

/*
* Copyright (C) 2017 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, see <http://www.gnu.org/licenses/>.
*
*/
#include "config.h"
#include "x11/window-x11.h"
#include "x11/window-x11-private.h"
window-xwayland: Add Xwayland fullscreen games workaround This is a workaround for X11 games which use randr to change the resolution in combination with NET_WM_STATE_FULLSCREEN when going fullscreen. Newer versions of Xwayland support the randr part of this by supporting randr resolution change emulation in combination with using WPviewport to scale the app's window (at the emulated resolution) to fill the entire monitor. Apps using randr in combination with NET_WM_STATE_FULLSCREEN expect the fullscreen window to have the size of the emulated randr resolution since when running on regular Xorg the resolution will actually be changed and after that going fullscreen through NET_WM_STATE_FULLSCREEN will size the window to be equal to the new resolution. We need to emulate this behavior for these games to work correctly. Xwayland's emulated resolution is a per X11 client setting and Xwayland will set a special _XWAYLAND_RANDR_EMU_MONITOR_RECTS property on the toplevel windows of a client (and only those of that client), which has changed the (emulated) resolution through a randr call. This commit checks for that property and if it is set adjusts the fullscreen monitor rect for this window to match the emulated resolution. Here is a step-by-step of such an app going fullscreen: 1. App changes monitor resolution with randr. 2. Xwayland sets the _XWAYLAND_RANDR_EMU_MONITOR_RECTS property on all the apps current and future windows. This property contains the origin of the monitor for which the emulated resolution is set and the emulated resolution. 3. App sets _NET_WM_FULLSCREEN. 4. We check the property and adjust the app's fullscreen size to match the emulated resolution. 5. Xwayland sees a Window at monitor origin fully covering the emulated monitor resolution. Xwayland sets a viewport making the emulated resolution sized window cover the full actual monitor resolution. https://gitlab.gnome.org/GNOME/mutter/merge_requests/739
2019-09-03 10:18:00 -04:00
#include "x11/xprops.h"
#include "wayland/meta-window-xwayland.h"
#include "wayland/meta-wayland.h"
enum
{
PROP_0,
PROP_XWAYLAND_MAY_GRAB_KEYBOARD,
PROP_LAST
};
static GParamSpec *obj_props[PROP_LAST];
struct _MetaWindowXwayland
{
MetaWindowX11 parent;
gboolean xwayland_may_grab_keyboard;
};
struct _MetaWindowXwaylandClass
{
MetaWindowX11Class parent_class;
};
G_DEFINE_TYPE (MetaWindowXwayland, meta_window_xwayland, META_TYPE_WINDOW_X11)
static void
meta_window_xwayland_init (MetaWindowXwayland *window_xwayland)
{
}
window-xwayland: Add Xwayland fullscreen games workaround This is a workaround for X11 games which use randr to change the resolution in combination with NET_WM_STATE_FULLSCREEN when going fullscreen. Newer versions of Xwayland support the randr part of this by supporting randr resolution change emulation in combination with using WPviewport to scale the app's window (at the emulated resolution) to fill the entire monitor. Apps using randr in combination with NET_WM_STATE_FULLSCREEN expect the fullscreen window to have the size of the emulated randr resolution since when running on regular Xorg the resolution will actually be changed and after that going fullscreen through NET_WM_STATE_FULLSCREEN will size the window to be equal to the new resolution. We need to emulate this behavior for these games to work correctly. Xwayland's emulated resolution is a per X11 client setting and Xwayland will set a special _XWAYLAND_RANDR_EMU_MONITOR_RECTS property on the toplevel windows of a client (and only those of that client), which has changed the (emulated) resolution through a randr call. This commit checks for that property and if it is set adjusts the fullscreen monitor rect for this window to match the emulated resolution. Here is a step-by-step of such an app going fullscreen: 1. App changes monitor resolution with randr. 2. Xwayland sets the _XWAYLAND_RANDR_EMU_MONITOR_RECTS property on all the apps current and future windows. This property contains the origin of the monitor for which the emulated resolution is set and the emulated resolution. 3. App sets _NET_WM_FULLSCREEN. 4. We check the property and adjust the app's fullscreen size to match the emulated resolution. 5. Xwayland sees a Window at monitor origin fully covering the emulated monitor resolution. Xwayland sets a viewport making the emulated resolution sized window cover the full actual monitor resolution. https://gitlab.gnome.org/GNOME/mutter/merge_requests/739
2019-09-03 10:18:00 -04:00
/**
* meta_window_xwayland_adjust_fullscreen_monitor_rect:
*
* This function implements a workaround for X11 apps which use randr to change the
* the monitor resolution, followed by setting _NET_WM_FULLSCREEN to make the
* window-manager fullscreen them.
*
* Newer versions of Xwayland support the randr part of this by supporting randr
* resolution change emulation in combination with using WPviewport to scale the
* app's window (at the emulated resolution) to fill the entire monitor.
*
* Apps using randr in combination with NET_WM_STATE_FULLSCREEN expect the
* fullscreen window to have the size of the emulated randr resolution since
* when running on regular Xorg the resolution will actually be changed and
* after that going fullscreen through NET_WM_STATE_FULLSCREEN will size
* the window to be equal to the new resolution.
*
* We need to emulate this behavior for these apps to work correctly.
*
* Xwayland's emulated resolution is a per X11 client setting and Xwayland
* will set a special _XWAYLAND_RANDR_EMU_MONITOR_RECTS property on the
* toplevel windows of a client (and only those of that client), which has
* changed the (emulated) resolution through a randr call.
*
* Here we check for that property and if it is set we adjust the fullscreen
* monitor rect for this window to match the emulated resolution.
*
* Here is a step-by-step of such an app going fullscreen:
* 1. App changes monitor resolution with randr.
* 2. Xwayland sets the _XWAYLAND_RANDR_EMU_MONITOR_RECTS property on all the
* apps current and future windows. This property contains the origin of the
* monitor for which the emulated resolution is set and the emulated
* resolution.
* 3. App sets _NET_WM_FULLSCREEN.
* 4. We check the property and adjust the app's fullscreen size to match
* the emulated resolution.
* 5. Xwayland sees a Window at monitor origin fully covering the emulated
* monitor resolution. Xwayland sets a viewport making the emulated
* resolution sized window cover the full actual monitor resolution.
*/
static void
meta_window_xwayland_adjust_fullscreen_monitor_rect (MetaWindow *window,
MetaRectangle *fs_monitor_rect)
{
MetaX11Display *x11_display = window->display->x11_display;
MetaRectangle win_monitor_rect;
cairo_rectangle_int_t *rects;
uint32_t *list = NULL;
int i, n_items = 0;
if (!window->monitor)
{
g_warning ("MetaWindow does not have a monitor");
return;
}
win_monitor_rect = meta_logical_monitor_get_layout (window->monitor);
if (!meta_prop_get_cardinal_list (x11_display,
window->xwindow,
x11_display->atom__XWAYLAND_RANDR_EMU_MONITOR_RECTS,
&list, &n_items))
return;
if (n_items % 4)
{
meta_verbose ("_XWAYLAND_RANDR_EMU_MONITOR_RECTS on %s has %d values which is not a multiple of 4",
window->desc, n_items);
g_free (list);
return;
}
rects = (cairo_rectangle_int_t *) list;
n_items = n_items / 4;
for (i = 0; i < n_items; i++)
{
if (rects[i].x == win_monitor_rect.x && rects[i].y == win_monitor_rect.y)
{
fs_monitor_rect->width = rects[i].width;
fs_monitor_rect->height = rects[i].height;
break;
}
}
g_free (list);
}
static void
meta_window_xwayland_force_restore_shortcuts (MetaWindow *window,
ClutterInputDevice *source)
{
MetaWaylandCompositor *compositor = meta_wayland_compositor_get_default ();
meta_wayland_compositor_restore_shortcuts (compositor, source);
}
static gboolean
meta_window_xwayland_shortcuts_inhibited (MetaWindow *window,
ClutterInputDevice *source)
{
MetaWaylandCompositor *compositor = meta_wayland_compositor_get_default ();
return meta_wayland_compositor_is_shortcuts_inhibited (compositor, source);
}
static void
meta_window_xwayland_get_property (GObject *object,
guint prop_id,
GValue *value,
GParamSpec *pspec)
{
MetaWindowXwayland *window = META_WINDOW_XWAYLAND (object);
switch (prop_id)
{
case PROP_XWAYLAND_MAY_GRAB_KEYBOARD:
g_value_set_boolean (value, window->xwayland_may_grab_keyboard);
break;
default:
G_OBJECT_WARN_INVALID_PROPERTY_ID (object, prop_id, pspec);
break;
}
}
static void
meta_window_xwayland_set_property (GObject *object,
guint prop_id,
const GValue *value,
GParamSpec *pspec)
{
MetaWindowXwayland *window = META_WINDOW_XWAYLAND (object);
switch (prop_id)
{
case PROP_XWAYLAND_MAY_GRAB_KEYBOARD:
window->xwayland_may_grab_keyboard = g_value_get_boolean (value);
break;
default:
G_OBJECT_WARN_INVALID_PROPERTY_ID (object, prop_id, pspec);
break;
}
}
static void
meta_window_xwayland_class_init (MetaWindowXwaylandClass *klass)
{
MetaWindowClass *window_class = META_WINDOW_CLASS (klass);
GObjectClass *gobject_class = G_OBJECT_CLASS (klass);
window-xwayland: Add Xwayland fullscreen games workaround This is a workaround for X11 games which use randr to change the resolution in combination with NET_WM_STATE_FULLSCREEN when going fullscreen. Newer versions of Xwayland support the randr part of this by supporting randr resolution change emulation in combination with using WPviewport to scale the app's window (at the emulated resolution) to fill the entire monitor. Apps using randr in combination with NET_WM_STATE_FULLSCREEN expect the fullscreen window to have the size of the emulated randr resolution since when running on regular Xorg the resolution will actually be changed and after that going fullscreen through NET_WM_STATE_FULLSCREEN will size the window to be equal to the new resolution. We need to emulate this behavior for these games to work correctly. Xwayland's emulated resolution is a per X11 client setting and Xwayland will set a special _XWAYLAND_RANDR_EMU_MONITOR_RECTS property on the toplevel windows of a client (and only those of that client), which has changed the (emulated) resolution through a randr call. This commit checks for that property and if it is set adjusts the fullscreen monitor rect for this window to match the emulated resolution. Here is a step-by-step of such an app going fullscreen: 1. App changes monitor resolution with randr. 2. Xwayland sets the _XWAYLAND_RANDR_EMU_MONITOR_RECTS property on all the apps current and future windows. This property contains the origin of the monitor for which the emulated resolution is set and the emulated resolution. 3. App sets _NET_WM_FULLSCREEN. 4. We check the property and adjust the app's fullscreen size to match the emulated resolution. 5. Xwayland sees a Window at monitor origin fully covering the emulated monitor resolution. Xwayland sets a viewport making the emulated resolution sized window cover the full actual monitor resolution. https://gitlab.gnome.org/GNOME/mutter/merge_requests/739
2019-09-03 10:18:00 -04:00
window_class->adjust_fullscreen_monitor_rect = meta_window_xwayland_adjust_fullscreen_monitor_rect;
window_class->force_restore_shortcuts = meta_window_xwayland_force_restore_shortcuts;
window_class->shortcuts_inhibited = meta_window_xwayland_shortcuts_inhibited;
gobject_class->get_property = meta_window_xwayland_get_property;
gobject_class->set_property = meta_window_xwayland_set_property;
obj_props[PROP_XWAYLAND_MAY_GRAB_KEYBOARD] =
g_param_spec_boolean ("xwayland-may-grab-keyboard",
"Xwayland may use keyboard grabs",
"Whether the client may use Xwayland keyboard grabs on this window",
FALSE,
G_PARAM_READWRITE);
g_object_class_install_properties (gobject_class, PROP_LAST, obj_props);
}