Do not try to treat types which are not kernel handles as kernel handles.

Do not try to treat types which are not kernel handles as kernel handles.

In particular, handle the case where an object has no name.

In theory, this should not happen for regular files, but SetSecurityInfo() is
almost certainly not supposed to care about that [i.e. this code probably
belongs in the server, at the very least]. However, fixing that will require
much more work.

While we're at it, rewrite the code to be a little more idiomatic about its
intent.

At least in the Windows 10 SDK.

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

Bump minimum version from 8.0 to 12.4, the minimum release supported
upstream. Streamline the FreeBSD section.

Signed-off-by: Connor McAdams <cmcadams@codeweavers.com>

uiautomationcore: Potentially raise focus event on the currently focused serverside provider in response to EVENT_OBJECT_FOCUS.
Signed-off-by: Connor McAdams <cmcadams@codeweavers.com>

uiautomationcore: Potentially raise focus event for serverside providers in response to EVENT_OBJECT_FOCUS.
Signed-off-by: Connor McAdams <cmcadams@codeweavers.com>

Signed-off-by: Connor McAdams <cmcadams@codeweavers.com>

Signed-off-by: Connor McAdams <cmcadams@codeweavers.com>

Signed-off-by: Nikolay Sivov <nsivov@codeweavers.com>

Also we don't care about the content of the buffer so using
HeapRealloc() makes no sense.

Otherwise it's impossible to know which iteration failed.

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

This mostly matters for Mac as segment CS is handled as a real LDT
entry.
Signed-off-by: Eric Pouech <epouech@codeweavers.com>

Signed-off-by: Eric Pouech <epouech@codeweavers.com>

Fixes cursor not being released when alt-tabbing out of an unresponsive
foreground window.

If the window is already fullscreen and its size is compatible with what
the compositor is requesting, don't force a resize, since some applications
are very insistent on a particular fullscreen size (which may not match
the monitor size).

Rename the function wayland_surface_configure_is_compatible to
wayland_surface_config_is_compatible to match the associated struct name.

The maximized and fullscreen states disallow surface contents that are
larger than the configured size. However, if we have a larger surface,
and only part of the surface contains useful client data, we can inform
the compositor using xdg_surface_set_geometry, so that only the
specified region is considered for compositor-side positioning and
state constraints.

We use the geometry to support the presentation of windows that insist
on particular positions and sizes which may not match the compositor's
requested size (e.g., fullscreen but may overshoot a few pixels outside
the monitor boundary).