February 2024 - Wine-GitLab

Re: [PATCH v4 0/2] MR4993: wbemprox: Reimplement LIKE. - approved
by Alexandre Julliard (＠julliard) Feb. 7, 2024

Feb. 7, 2024

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4993

1 0

Re: [PATCH v6 0/1] MR4985: windows.globalization: Add IIterable_HSTRING impl to IVectorView_HSTRING. - approved
by Alexandre Julliard (＠julliard) Feb. 7, 2024

Feb. 7, 2024

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4985

1 0

Re: [PATCH v2 0/1] MR5045: wbemprox: Add property 'Caption' to Win32_DiskDrive. - approved
by Alexandre Julliard (＠julliard) Feb. 7, 2024

Feb. 7, 2024

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5045

1 0

Re: [PATCH v3 0/5] MR4981: Playback of wave tracks with loops. - approved
by Alexandre Julliard (＠julliard) Feb. 7, 2024

Feb. 7, 2024

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4981

1 0

[PATCH v3 0/2] MR4993: wbemprox: Reimplement LIKE.
by Arek Hiler (＠ivyl) Feb. 7, 2024

Feb. 7, 2024

Current implementation handles correctly % only at the end of the string. Nothing else matches. The new implementation while naïve and recursive handles both _ and * correctly. -- v3: wbemprox: Reimplement LIKE. wbemprox/tests: Test LIKE queries. https://gitlab.winehq.org/wine/wine/-/merge_requests/4993

3 4

[PATCH 0/1] MR5051: user32/tests: Fix flags on expected EM_GETPASSWORDCHAR message.
by Esme Povirk (＠madewokherd) Feb. 7, 2024

Feb. 7, 2024

I missed that a few of these had the defwinproc flag when initially adding them. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5051

2 1

[PATCH v2 0/5] MR4981: Playback of wave tracks with loops.
by eric pouech (＠epo) Feb. 7, 2024

Feb. 7, 2024

This serie mainly tackles the playback of wave tracks with loops. Current code had to be improved as: - loop playback doesn't require setting the loop start/end points: leaving them at 0 mean playing the whole segment, - moreover, the length (at least for wave tracks) of the segment is not used. Instead, the duration of stamped/posted tracks is used instead. - even forcing a length on segment isn't taken into account (tested locally, but not included in the current tests). - implemented it by creating the graph internal to segment state and gathering relevant information on the fly. There's no indication it's done this exact way on native, but at least tests for time of track playback are identical. Notes: - only changed the track waves, future work will require equivalent testings at least on MIDI sequences. -- v2: dmime: Use sent duration in loop's playback. dmime: Generate track flags while in loop. dmime: Add IDirectMusicGraph interface to segment state. dmime: Add tests about segment state's graph interface. dmime: Fully implement IDirectMusicSegmentState::GetRepeats(). https://gitlab.winehq.org/wine/wine/-/merge_requests/4981

3 8

[PATCH v2 0/1] MR5047: server, ntdll: Use 64 bit for unix thread id.
by Marc-Aurel Zent (＠mzent) Feb. 7, 2024

Feb. 7, 2024

This is in preparation for the mach thread id rework, which requires 64 bit there (and incidentally also stops truncating the FreeBSD one). There wasn't any direct usage of `__int64` in the sever protocol before, so I added a new typedef and a new `dump_int64()` function (not sure if needed per se though). -- v2: server, ntdll: Use 64 bit for unix thread id. https://gitlab.winehq.org/wine/wine/-/merge_requests/5047

4 4

Re: [PATCH v11 0/7] MR4082: gdiplus: Implement font linking in GdipDrawString.
by Santino Mazza (＠tati1454) Feb. 7, 2024

Feb. 7, 2024

On Tue Feb 6 18:34:36 2024 +0000, Esme Povirk wrote: > The difference might have to do with scaling? It looks like > GdipMeasureString scales the size, and I don't think > font_link_get_text_extent_point would. > Come to think of it, it's probably necessary to account for text > rotation when in draw_string_callback (an arbitrary affine transform can > be applied to the text, although I think at the moment our handling of > anything beyond rotation is a bit broken). I think it might be a good > idea to add output parameters for dx and dy to draw_driver_string. About text rotation in draw_string_callback, should it be included in this merge request? dx and dy refers to direction? And where would they come from in draw_driver_string? -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4082#note_60518

1 0

[PATCH 0/1] MR5050: kernelbase: Copy the read-only attribute from the source.
by Gabriel Ivăncescu Feb. 7, 2024

Feb. 7, 2024

-- https://gitlab.winehq.org/wine/wine/-/merge_requests/5050

1 1