The rawinput patches in wine-staging require the drivers to send
INPUT_MOUSE and INPUT_KEYBOARD events with a non-NULL rawinput
parameter. Since the rawinput parameter is currently ignored in
upstream for such events, apply this change to maintain a unified
codebase across upstream and staging.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Use a standalone systray, adapted from winex11, to present icons for
applications.

Because the context menu on icons is drawn using global positioning
across process boundaries, we cannot currently anchor the menu window
properly to its effective parent (i.e., the icon), and we draw it as a
toplevel instead. Practically this has the effect that the menu window
will be placed at arbitrary locations on the screen by the Wayland
compositor.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

During development it's often useful to be able inspect the contents and
window or damage regions of the various buffers involved in software
rendering.

This commit adds helper functions to dump buffer contents to disk, and
uses them to dump the window buffer at flush time, the wayland SHM
buffers at commit time, and the front buffer at update/glFlush time.

These helpers are turned off by default and can be enabled by changing
the value of the corresponding preprocessor define.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Introduce a mechanism to select whether we should use application-side
or composidor-side scaling. This is controlled by the "HiDPIScaling"
global or per-app driver option, either "Application" (the default) or
"Compositor".

With application-side scaling, which is the default, the application has
access to the full/native resolution of the outputs, and needs to manage
scaling manually (e.g., by using the Wine DPI options).

With compositor-side scaling, the application has access only to the
scaled resolution of the outputs, and the compositor automatically
scales the provided buffers.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Relay the event to the IDropTarget at the current drag-and-drop position,
which will then initiate a data transfer by using the IDataObject_GetData
implementation for the associated Wayland data offer.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Relay the event to the IDropTarget at the new drag-and-drop position,
and notify the Wayland compositor of any accepted format/mime type and
actions.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Relay the event to the IDropTarget at the current drag-and-drop
position.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Relay the event to the IDropTarget at the enter position, and notify the
Wayland compositor of any accepted format/mime type and actions.

The accepted mime type is set indirectly through IDropTarget_DragEnter
eventually calling our IDataObject_(Query)GetData implementation for the
associated data offer.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Implement functions to find the IDropTarget for a particular point in a
window.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

For each mime type of the associated data offer we provid a FORMATETC
entry with the matching Windows clipboard format. We ensure that there
are no duplicate FORMATETC entries.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

If the associated data offer has a mime type matching the requested
Windows clipboard format, import the data into a HGLOBAL memory object.

Check if for any of the available mime types of the associated data
offer we support converting from that mime type to the requested Windows
clipboard format.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

This IDataObject will be used to integrate with drag-and-drop
from other Wayland clients.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Handle the Wayland event which informs us of the new current clipboard
selection. We use the provided event information to update the available
formats in the Windows clipboard, without populating them with any
actual data. We populate the clipboard data on demand through the
handling of the WM_RENDERFORMAT message.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

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

Import into Windows clipboard data we got from other Wayland clients,
for a particular Windows clipboard format. This allow us to fetch
clipboard data and populate the Windows clipboard contents on demand.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

When the Windows clipboard is updated, create a new Wayland data source
that exports the update clipboard data, and make it the current
Wayland data selection.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Import and export TIFF, PNG, JPEG and GIF image formats.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Convert between CF_HDROP Windows clipboard format and "text/uri-list"
Wayland clipboard format.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Import and export RTF clipboard/drag-and-drop data.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Convert between CF_UNICODETEXT clipboard format and common
"text/plain" Wayland clipboard formats.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Add a function that ensures that all data is written to a file
descriptor, resuming in case of interruptions or partial writes.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Introduce infrastructure to convert clipboard/drag-and-drop data
between what Wayland understands and what Wine understands.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

The clipboard window is created in the PE code, initiated by a driver
kernel callback invoked from the unixlib side. Clipboard messages
are received in the PE side and forwarded to the unixlib side to
be handled there.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

This mechanism allows the unixlib code of the driver to call back into
the PE code.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Keep track of the wl_data_offer objects sent by the Wayland compositor,
and their properties.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

This will evolve to support clipboard and drag-and-drop operations in
upcoming commits.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

When the Wayland surface is updated (including when it changes to NULL,
i.e., when it is destroyed), we need to notify the application so that
it can deal with it accordingly.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

The VkSurfaceKHR we return in wayland_vkCreateWin32SurfaceKHR *is* the
native VkSurfaceKHR, so the implementation is trivial.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

This is a simple passthrough implementation to the native Vulkan driver.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

This is a simple passthrough implementation to the corresponding Vulkan
Wayland extension.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

This is a simple passthrough implementation to the native Vulkan driver,
with the addition of a VkSurfaceKHR invalidation check.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

This is a simple passthrough implementation to the native Vulkan driver,
with the addition of a VkSurfaceKHR invalidation check.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Passthrough implementations with two additions:

1. Checking for invalidated VkSurfaceKHR.
2. Try to emulate vkGetPhysicalDeviceSurfaceFormats2KHR with
   vkGetPhysicalDeviceSurfaceFormatsKHR if needed.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Passthrough implementations with three additions:

1. Checking for invalidated VkSurfaceKHR.
2. Try to emulate vkGetPhysicalDeviceSurfaceCapabilities2KHR with
   vkGetPhysicalDeviceSurfaceCapabilitiesKHR if needed.
3. Set the capabilities' image extent values to match what the Vulkan Win32 WSI
   typically provides.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

This is a simple passthrough implementation to the native Vulkan driver.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

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

This is a simple passthrough implementation to the native Vulkan driver,
with the addition of a VkSurfaceKHR invalidation check.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Return the native instance extension properties, substituting
VK_KHR_wayland_surface for VK_KHR_win32_surface.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

When the Wayland surface associated with a Vulkan surface or swapchain
is scheduled for destruction, we mark such Vulkan objects as invalidated
in the driver and callers are notified with the
VK_ERROR_SURFACE_LOST_KHR hard error when they try to use such objects.

Note that the Vulkan objects hold a reference to the associated Wayland
surface, so there is no danger of time-of-check to time-of-use (TOCTOU)
related bugs/races when checking for invalidation.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>