The Vulkan specification does not currently mandate this. However, an
(unfortunately internal) Khronos discussion determined that this is an
oversight, and that many drivers likely expect that no counter buffer will be
bound if no XFB buffer is bound. Accordingly the specification will probably
mandate this in the future.

lavapipe is such a driver. This fixes a crash with llvmpipe in
test_index_buffer_offset().

If DISCARD maps are accelerated, passing empty map flags won't return the same accelerated BO.

Tested with Port Royale 2 and Rayman 3.

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=55770

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=47609

Fixes incorrect EG key number scale and offset that caused missing
lower notes of some instruments (e.g. Acoustic Grand Piano).

This allows loaded instruments to take effect without a subsequent
program change. In particular, when there is no program change at all,
this allows the default Acoustic Grand Piano or Standard drum set to
play. As a side effect, this disables FluidSynth fallback logic for
missing presets.

Instead of checking it in set_report_from_joystick_event.

Signed-off-by: Dmitry Timoshkov <dmitry@baikal.ru>

user32/tests: Add some tests for font charset returned by SPI_GETICONTITLELOGFONT and SPI_GETNONCLIENTMETRICS.
Signed-off-by: Dmitry Timoshkov <dmitry@baikal.ru>

This prevents Native Instruments Kontakt 7 from crashing on start-up.

Spotted by Rémi Bernon.

Due to the asynchronous nature of Wayland events, and the design of the
xdg_toplevel protocol, an xdg configure event may be a reaction to a
request in the application's configuration past, and the size hint may
be out of date. For example:

1. The client commits a 100x100 buffer to a surface.
2.1 The compositor sends xdg configure(100x100, state=activated).
2.2 In the meantime, the client resizes and commits a 50x50 buffer.
3. The client receives the event from (2.1). If we respect the
   size hint, we will resize back to 100x100, although this was
   neither the client's nor the compositor's intention.

To mitigate this we ignore size hints for states that do not
require strict size adherence.

Take into account the window scale factor and use wp_viewport to
instruct the compositor to present cursors with that scale.

Take into account the window scale factor and use wp_viewport to
instruct the compositor to present surfaces at that scale.

Introduce and use functions to convert between the window logical and
Wayland surface coordinate spaces. At the moment the two are the same
but this will change with the introduction of scaling support.

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=55660

Assume that the window rect passed NtUserIsWindowRectFullScreen is
expressed in terms of thread dpi and convert monitor rects accordingly
for proper matching.