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
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
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
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