- 06 Nov, 2019 5 commits
-
-
Zebediah Figura authored
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=40950Signed-off-by:
Zebediah Figura <z.figura12@gmail.com> Signed-off-by:
Alexandre Julliard <julliard@winehq.org>
-
Zebediah Figura authored
Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
-
- 05 Nov, 2019 33 commits
-
-
Alistair Leslie-Hughes authored
Signed-off-by:
Alistair Leslie-Hughes <leslie_alistair@hotmail.com> Signed-off-by:
Michael Stefaniuc <mstefani@winehq.org> Signed-off-by:
-
Louis Lenders authored
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=24529Signed-off-by:
Louis Lenders <xerox.xerox2000x@gmail.com> Signed-off-by:
-
Zhiyi Zhang authored
After 25167fb2 get_primary_monitor_rect() returns an empty rectangle before X11DRV_DisplayDevices_Init() is called. So use get_host_primary_monitor_rect() to get the current X desktop size. It's also more intuitive this way. Signed-off-by:
Zhiyi Zhang <zzhang@codeweavers.com> Signed-off-by:
-
Zhiyi Zhang authored
After 25167fb2, get_primary_monitor_rect(), which is used in is_window_rect_fullscreen(), may return the primary screen size set by the last explorer instance if wineserver didn't fully shuts down. Also get_primary_monitor_rect() no longer reports the host primary monitor rect before virtual desktop initialization now. So move the desktop fullscreen check after desktop initialization so that primary screen size is updated and valid. Signed-off-by:
-
Zhiyi Zhang authored
After 25167fb2, get_primary_monitor_rect() maybe invalid before display device initialization or returns the desktop rectangle after desktop initialization in virtual desktop mode, which is wrong. The desktop size limit should come from host system. This fixes a regression from efbbe666. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=47815Signed-off-by:
-
Zhiyi Zhang authored
If we want to query host monitor dimensions, we need to use XRandR or Xinerama handler. However when in virtual desktop mode, its display device handler overrides other handlers. So we need to separate them. Then we can implement features that require host monitor dimensions like checking whether the virtual desktop window is fullscreen. Signed-off-by:
-
Zhiyi Zhang authored
Signed-off-by:
-
Sven Baars authored
Signed-off-by:
Sven Baars <sven.wine@gmail.com> Signed-off-by:
Jacek Caban <jacek@codeweavers.com> Signed-off-by:
-
Rémi Bernon authored
The window created in the separate thread in test_Input_mouse sometimes fails to catch the mouse input in time. Waiting and flushing the initial messages seems to make the issue harder to reproduce. Signed-off-by:
Rémi Bernon <rbernon@codeweavers.com> Signed-off-by:
-
Alistair Leslie-Hughes authored
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=47945Signed-off-by:
-
Jacek Caban authored
Be more explicit about what applies only to non-global code. Signed-off-by:
-
Jacek Caban authored
If it's an implicit this, we can handle that in interp_me. Signed-off-by:
-
Jacek Caban authored
Signed-off-by:
-
Jacek Caban authored
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=41119Signed-off-by:
-
Jacek Caban authored
Signed-off-by:
-
Jacek Caban authored
Signed-off-by:
-
Jacek Caban authored
Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
Nikolay Sivov <nsivov@codeweavers.com> Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
-
Vincent Povirk authored
This fixes a bug where some verions of mingw and probably gcc assume that the result of pointer subtraction will be non-NULL, causing MSI_OpenDatabaseW to break when given the mode MSIDBOPEN_READONLY + MSIDBOPEN_PATCHFILE. Signed-off-by:
Vincent Povirk <vincent@codeweavers.com> Signed-off-by:
Hans Leidekker <hans@codeweavers.com> Signed-off-by:
-
Alexandre Julliard authored
Signed-off-by: -
Alexandre Julliard authored
Signed-off-by: -
Alexandre Julliard authored
Signed-off-by: -
Alexandre Julliard authored
Signed-off-by:
-
- 04 Nov, 2019 2 commits
-
-
Zebediah Figura authored
For some reason, on fvwm2 sometimes focus_window will be restored and activated between the subsequent call to SetForegroundWindow() and the next call to ShowWindow(SW_RESTORE), causing the next test to fail. Flushing first seems to reliably work around this. Signed-off-by:
Henri Verbeet <hverbeet@codeweavers.com> Signed-off-by:
-
Zebediah Figura authored
llvmpipe is extraordinarily slow to execute glBeginQuery() [as much as 10ms per call] when the regression test for bug 45932 is run after the previous test drawing a 33-bit number of samples. Swap the two tests to work around this. Signed-off-by:
-
