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
Freetype's FT_Load_Glyph may return different glyph metrics (in particular, horiAdvance) depending on load target flags (FT_LOAD_TARGET_MONO, FT_LOAD_TARGET_NORMAL ...). Among the consequences of that are:
- the size of, e. g, GetTextExtentPoint() doesn't match the size of actually rendered text;
- DrawTextW() with DT_CALCRECT flag returns wrong bounding rectangle.
In the core of that is GetGlyphOutline() returning different values for GGO_METRICS format (used in various glyph metrics query functions) and the actual format used during rendering.
It probably make sense to use effective fonts rendering option for GGO_METRICS so that matches. I did some ad-hoc testing on Windows with currently problematic Tahoma font and quite expectedly GetGlyphOutline(GGO_METRICS) always returns the same metrics as other output format options. While all the options also have the same metrics between each other (which is still not the case with Wine). I guess it is not easily possible to make all the face load options match each other with freetype (nor I am sure that is always the case on Windows for all the possible fonts), but making GGO_METRICS return the metrics matching actual gdi device context setup looks more important.
Fixes Idle Spiral being unable to render typed text in save / load dialogs (which is using Winforms from Unity's Mono).
--
v2: win32u: Use font AA flags when querying glyph outline with GGO_METRICS.
d3dx9/tests: Make test_ID3DXFont() less dependent on GetGlyphOutlineW(GGO_METRICS) behaviour.
https://gitlab.winehq.org/wine/wine/-/merge_requests/4406