I'm confused about why "scripting" is a concern here. Do any scripts currently parse the *text* output, which is currently localized, and redundant with the return value anyway? Would changing that to MESSAGE actually keep compatibility in that case?
I think it probably makes sense to keep console output for the sake of clear communication, but I don't understand why scripting.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/4440#note_53135
This part introduces support for Vulkan swapchains to the Wayland driver:
* Implement several Vulkan functions typically called to get info before swapchain creation.
* Implement swapchain creation/destruction
* Implement getting swapchain images.
I stopped short of adding presentation support since the MR would grow too big (stay tuned for part 10.3).
Thanks!
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/4456
This program is in GUI subsystem, but expects I/O
with Unix console. This is a Wine specific behavior.
So explicitely use unix fd instead of the inherited
standard handles.
Wine-Bugs: https://bugs.winehq.org/show_bug.cgi?id=55723
Signed-off-by: Eric Pouech <epouech(a)codeweavers.com>
--
v2: regedit: Use message boxes by default for output.
regsvr32: Use message boxes by default for output.
https://gitlab.winehq.org/wine/wine/-/merge_requests/4440