If allocator fails, native returns NS_E_NO_MORE_SAMPLES whereas we propagate the allocator's failure
code. Some games checks this return value and will raise an error/exception if anything other than
NS_E_NO_MORE_SAMPLES is returned, for example any game using the KiriKiri movie player [0] will do
this.
[0]: https://github.com/krkrz/krkrz/blob/fd5c4baa6a2ef5978db1bd043634351f48667da…
--
v3: winegstreamer: Return NS_E_NO_MORE_SAMPLES from WMSyncReader if sample fails to read.
https://gitlab.winehq.org/wine/wine/-/merge_requests/9249
This serie ensures that a module loaded in dbghelp with
SLMFLAG_NO_SYMBOLS always doesn't load symbol (except the ones
from the EXPORT table of the PE image).
To be implemented correctly, it requires a refactoring of
the way dbghelps looks up for a debug format.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/9284
It's a dependency of !9209. I'm not sure yet if more changes are needed on ucrtbase/msvcp140 side.
--
v2: msvcrt: Call __DestructExceptionObject() in __ExceptionPtrDestroy.
https://gitlab.winehq.org/wine/wine/-/merge_requests/9285
On Sun Oct 26 12:05:40 2025 +0000, Michael Stefaniuc wrote:
> -600 looks like a magic constant. How did you get to that number?
By trying different values and comparing the volume by ear. I can probably make an interactive test for this.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/9259#note_119699
There exist clients that disable hardware cursors, and instead draw a
software cursor during their renderloop. Such clients incorrectly cause
winewayland to enable relative pointer motion because winewayland thinks
the cursor is not visible, when it is in fact visible and just drawn by
the client instead.
Enabling relative pointer motion breaks compositors that simulate
wl_pointer from tablet tool motion. sway is one such compositor that
supports sending wl_pointer events for clients that don't understand
tablet-v2.
Fix this by not discarding absolute motion events even in the case that
relative pointer motion is active. When relative pointer was
implemented, winewayland didn't support SetCursorPos and accepting
absolute motion events would break mouselook in 3D games. However, now
it does support SetCursorPos so there should be no harm in accepting
absolute motion events as well.
This allows tablet devices to work with winewayland running badly
behaved clients that do software rendering of cursors on compositors
that do simulate wl_pointer from tablet motion, despite winewayland not
supporting tablet-v2 yet.
Signed-off-by: Gopal Prasad <llyyr.public(a)gmail.com>
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/9068