GitLab

The subsurface position is double-buffered state of the parent
surface. When positioning a subsurface commit the parent surface for
the position to take effect.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Set the main output and scale of wayland subsurfaces at creation time
and ensure it remains up to date.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

We use heuristics to decide which toplevels are to be considered
transient (and thus be backed by wayland subsurfaces): the toplevel
needs to be undecorated and have a reasonably small size relative
to its main monitor.

In some cases transient windows using global coordinates are created
once and then moved around and shown as needed. This means that we
cannot decide the effective parent only at creation time, but rather
keep track of the current effective parent to be able to place such
transient windows at the correct surface-local positions.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

When notifying about a Wine mode change we need to send an internal
event to all threads. Use the per-thread clipboard window as the
recipient of the message since we know it always exists for all
Wayland/GUI threads.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Set the initial position and size of GL/VK subsurfaces to match the
client rectangle.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

We may need to create/destroy GL/VK wayland subsurfaces, as a result of
creating/destroying GL/VK surface types, from arbitrary threads. Handle
such operations in a more thread safe manner.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Implement support for the ChangeDisplaySettings(NULL, NULL, ...) call,
which instructs us to restore all monitors to registry settings.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Add a driver registry option "HiDPIScaling" to select between
"Application" scaling (the default) and "Compositor" scaling. Enabling
compositor scaling lets the Wayland compositor transparently scale
surfaces according to the output scale factor.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Always use the native/HiDPI resolution for window rendering, even when
the surface backing the window is presented on a scaled wayland output.
This provides the full resolution to applications.

To achieve this we inform the wayland compositor that our surfaces are
already scaled for the output they are in. We update this scaling
information only when a surface moves *fully* to a new output. Until
this move happens, e.g., when a surface is between outputs, we maintain
the current scaling,
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Handle the addition and removal of monitors and their integration
with window management.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Ensure coordinates are properly transformed between wayland
surface-local coordinate space and wine coordinate space as
needed.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Make coordinate transformation functions more accurate by avoiding
intermediate rounding or decimal truncation when possible during
calculations.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Don't update the window focus as a response to wl_keyboard enter events,
as this may confuse Wine, especially when dealing with input to popups.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Handle errors during wayland_read_events() and terminate the application
if an unrecoverable error occurs.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

During surface destruction only dispatch events if we we are in the same
thread that handles the window. Otherwise we will call wayland event
handlers in an arbitrary thread, a scenario which we do not support.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Destroy the thread wayland event queues last since other operations
during shutdown may use them (e.g., roundtrips during surface
destruction).

Also, destroy any remaining surfaces before xdg_wm_base to avoid
protocol errors.

Finally, don't destroy any GL/VK subsurface when destroying the
parent surface. Since GL/VK subsurfaces hold a reference to the
parent they never outlive the parent, and during shutdown
all surfaces are now destroyed explicitly.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Remove manual tracking of parent surface of GL/VK subsurfaces.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Use the output name, if available, to calculate a unique id for each
output. This ensures that output ids are not dependent on the compositor
report order of wl_outputs. Retain the previous approach of assigning
sequential ids as a fall back.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

When a user requests enumeration of the registry display settings and no
settings are found, use the native mode of the display as the
fallback/default mode.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Implement heuristics based on the current cursor clip and cursor
visibility to determine when and how to confine a pointer and emit
relative motion events.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Do not assume that a pointer interface object is always present.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

In contrast with the Wine X11 Vulkan driver, we provide the native
handle for VkSurfaceKHR (and VkSwapchainKHR) to the layers above.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Support recreating the internal window state when the backing wayland
surface changes, while maintaining any GL related objects.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

In order for the fullscreen state, or a surface size change while
fullscreen to be applied by the wayland compositor, the clients are
required to commit a new buffer for the fullscreen toplevel.

There are some scenarios when the toplevel window surface contents are
not invalidated when transitioning to fullscreen, so the proper wayland
state is not set. Fix this by detecting such state transitions and
invalidating the window surface to ensure we eventually commit a new
buffer.

Such a scenario can occur with the upcoming Vulkan support, where the
the Vulkan window contents are implemented with a subsurface of the
toplevel decoration surface. During a fullscreen state change the
toplevel surface may not be updated, so we need to force an invalidation
as described above.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Track the active users of wayland surfaces using reference counts. This
is going to be useful in upcoming commits introducing Vulkan support,
due to related lifetime guarantees imposed by the Vulkan API.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

We currently have no need to maintain internal state for the desktop
window.  This also avoids inadvertently backing the desktop window with
a wayland surface and presenting it on screen.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

The contents of GL or Vulkan windows are rendered on subsurfaces
with the parent surface used for the decorations. Such GL/VK
subsurfaces may want to commit their contents before the parent
surface has had a chance to commit. In such cases the GL/VK commit
will not be displayed, but, more importantly, will not get a frame
callback until the parent surface is also committed. Depending on
the presentation mode, a second GL/VK buffer swap may indefinitely
block waiting on the frame callback.

This commit introduces a function to ensure that a wayland surface
is mapped, by committing a dummy buffer if necessary. This function
is called before GL swap buffers operations to ensure the swap cannot
block indefinitely as described above.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Perform a more thorough check of the dependencies of the Wayland driver
during configure.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Use the keymap information provided by the compositor to map keys in the
driver.

Note that changing the keymap from the Windows/Wine side is not
currently supported.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Add an extra wayland roundtrip during initialization to ensure events
from third-order event registrations (like for wl_keyboard) are handled
before finishing initialization.

This is important for cases where the wayland thread data is initialized
in a call that immediately needs to access such wayland data. For
example, in upcoming commits, win32 key mapping functions may need to
initialize wayland thread data and immediately use keymap information.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Shaped windows, either through window regions or layered, require
ARGB buffers. Ensure that we always back our surfaces with the correct
buffer type.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

We want unconditionally update the window surface passed by Wine.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Layered window surfaces are implemented with ARGB surfaces with src
alpha.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

This is a special where the case where the destination wayland buffer is
ARGB but the source wine surface is RGB. Such buffers require special
handling while transferring data to ensure we have valid alpha values.

This is going to be useful in upcoming commits that use this mechanism
to properly support window regions.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Don't rely on window data being accurate when calling
set_surface_region(), since it may be called before window rect data is
valid, e.g., when recreating a surface during a
WAYLAND_WindowPosChanging invocation.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

It's a protocol error to submit a surface geometry of 0x0.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Check for and recreate the backing window data when a window's parent
changes. Since children windows don't get their own wayland surface,
this may involve creating or destroying the backing wayland depending
on the type of change.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>