Some Wine tests are multi-threaded or start child processes which can
result in traces and failure messages being garbled which prevents them
from being recognized by continuous integration tools.
So printing the tests messages is now serialized. Note that if a process
crashes while holding the mutex, that mutex will be abandonned and not
cause a deadlock.
--
v5: tests: Make sure only one thread prints traces at a time.
https://gitlab.winehq.org/wine/wine/-/merge_requests/734
This lets WINETEST_COLOR works under Windows console (at least, on recent
versions where ANSI support is available).
(Keeping logic:
+ "auto": emit ANSI sequences only when output is capable of
+ "1": always use ANSI sequences
)
Signed-off-by: Eric Pouech <eric.pouech(a)gmail.com>
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/759
This is confirmed by the tests in test_scrollbar() and manual tests on XP. Even though scrollbar
arrows and thumb are in fact transparent, DrawThemeParentBackground() is not called to paint the
parent background, leaving the transparent area untouched. On Windows, even if the scrollbar arrows
are reported to be transparent, the bitmaps for arrow parts in the stock themes are in fact opaque.
Fix Ice Cream Calculator slow scrolling after 4cb229a because the WM_PRINTCLIENT handling in the
application is slow.
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=53337
--
v2: comctl32/datetime: Do not paint parent background when painting arrows.
uxtheme: Do not draw parent background even if scrollbar arrows and thumb are transparent.
uxtheme: Use the brush from WM_CTLCOLORSCROLLBAR to paint SB_CTL scrollbar tracks if present.
comctl32/tests: Add themed scrollbar background tests.
uxtheme/tests: Add theme tests.
https://gitlab.winehq.org/wine/wine/-/merge_requests/755
On Sat Aug 27 11:18:20 2022 +0000, Matteo Bruni wrote:
> Nah, let's just keep this as it is now, no reason to make everything
> more complicated.
> I guess this is just something peculiar to fx_4_0 effects, surprised
> that I never encountered it before. I'll do some further digging locally.
I found that in d3d10/tests/effect.c: create_effect():
> /*
> * Don't use sizeof(data), use data[6] as size,
> * because the DWORD data[] has only complete DWORDs and
> * so it could happen that there are padded bytes at the end.
> *
> * The fx size (data[6]) could be up to 3 BYTEs smaller
> * than the sizeof(data).
> */
Maybe we could do something like this? Use DWORDs to store shader code. And pass data[6] to size argument.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/697#note_7431
This is confirmed by the tests in test_scrollbar() and manual tests on XP. Even though scrollbar
arrows and thumb are in fact transparent, DrawThemeParentBackground() is not called to paint the
parent background, leaving the transparent area untouched. On Windows, even if the scrollbar arrows
are reported to be transparent, the bitmaps for arrow parts in the stock themes are in fact opaque.
Fix Ice Cream Calculator slow scrolling after 4cb229a because the WM_PRINTCLIENT handling in the
application is slow.
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=53337
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/755
Made changes to comdlg32/itemdlg.c to add missing controls, which are the address bar and the up button.
Updated bitmaps in comctl32 and SVG files for history icons.
My changes help to resolve this bug: https://bugs.winehq.org/show_bug.cgi?id=50338.
--
v13: comdlg32: Add missing controls to the common item dialog, only affecting the implementation
comdlg32: Add missing controls and their functionality to IFileDialog, or the common item dialog.
https://gitlab.winehq.org/wine/wine/-/merge_requests/672