Anyway, it's a pain that we have to maintain two MS symbols
demanglers (this one and the one in dlls/msvcrt).
Signed-off-by: Eric Pouech <epouech@codeweavers.com>

From the tests it behaves more like a semaphore than like an event.

I'm not testing explicitly because I'm not sure it's relevant, but
another indication is that calling ReleaseSemaphore() returns
ERROR_ACCESS_DENIED, while calling SetEvent() returns
ERROR_INVALID_HANDLE.

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: Connor McAdams <cmcadams@codeweavers.com>

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

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

Since setting the current mode also sets the registry settings (if not
already set), we also remove the code that manually changes the registry
settings.

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

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

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

Since setting the current mode also sets the registry settings (if not
previously set), we also remove the code that manually changes the
registry settings.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

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

Update the gdi_device_manager API to enable drivers to set the current
mode (along with the registry mode if not already set) in
UpdateDisplayDevices.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

The failing test was garbled by remaining debug events from previous test.
Signed-off-by: Eric Pouech <epouech@codeweavers.com>