So it's possible to easily debug deadlocks involving the Internal ROT object
Signed-off-by: Lorenzo Ferrillo <lorenzofersteam@live.it>

Sometimes umarshalling an object from the RunningObjectTable can cause the routine to access the
table back inside another thread, causing a deadlock.
Visual Studio 2019 is an example of this behaviour.
Signed-off-by: Lorenzo Ferrillo <lorenzofersteam@live.it>

Signed-off-by: Gabriel Ivăncescu <gabrielopcode@gmail.com>

Signed-off-by: Gabriel Ivăncescu <gabrielopcode@gmail.com>

Signed-off-by: Gabriel Ivăncescu <gabrielopcode@gmail.com>

Signed-off-by: Gabriel Ivăncescu <gabrielopcode@gmail.com>

Signed-off-by: Gabriel Ivăncescu <gabrielopcode@gmail.com>

Signed-off-by: Gabriel Ivăncescu <gabrielopcode@gmail.com>

Signed-off-by: Gabriel Ivăncescu <gabrielopcode@gmail.com>

Just use the dispex's query_interface.
Signed-off-by: Gabriel Ivăncescu <gabrielopcode@gmail.com>

Signed-off-by: Gabriel Ivăncescu <gabrielopcode@gmail.com>

Signed-off-by: Gabriel Ivăncescu <gabrielopcode@gmail.com>

Signed-off-by: Gabriel Ivăncescu <gabrielopcode@gmail.com>

Windows v1709 has a bug that breaks GetClassLong on a
different desktop from where the class was registered.

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

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

Changing the colour of the second pixel of the source bitmap clarifies
the incorrect behaviour of PixelOffsetMode Half and HighQuality.

This also provides better proof that PixelOffsetMode None and Fast are
implemented correctly.