January 2025 - Wine-GitLab - list.winehq.org

Re: [PATCH v10 0/6] MR6569: winex11: Refactor window state/config tracker to fix race conditions.
by Patrick Laimbock (＠Patrick) Jan. 16, 2025

Jan. 16, 2025

> I don't want to break something else this late. That makes total sense :smiley: I'm happy to test anything so feel free to ping me. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/6569#note_92038

1 0

Re: [PATCH v10 0/6] MR6569: winex11: Refactor window state/config tracker to fix race conditions.
by Rémi Bernon Jan. 16, 2025

Jan. 16, 2025

On Thu Jan 16 11:31:22 2025 +0000, Patrick Laimbock wrote: > Hi Rémi. With the change below (bug51357.patch) from > https://bugs.winehq.org/show_bug.cgi?id=51357 the wrong mouse offset is > fixed in the VST plugin's main window titled 'Spire'. But, e.g. clicking > the 'menu' button shows the menu in the wrong place. See screenshot. The > menu should appear below the 'menu' button (top row) in the window > titled 'Spire'. So the change above does not fix the issue but hopefully > it gives you an idea what the problem might be. If you need more > information please let me know. Thanks! > [bug51357.patch](/uploads/dea8a1e711846f7e7642c16eacd284b4/bug51357.patch) > ![Screenshot_From_2025-01-16_11-49-56](/uploads/decbb70d2abc1b99d3fd28e0b6382080/Screenshot_From_2025-01-16_11-49-56.png) Thank you! Yes, I think we could consider doing something like and use window-relative coordinates all the time, now that we're better tracking the X window tree position, and stopped using XTranslateCoordinates. It would have to wait until Wine 10 is released though, I don't want to break something else this late. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/6569#note_92037

1 0

Re: [PATCH v10 0/6] MR6569: winex11: Refactor window state/config tracker to fix race conditions.
by Patrick Laimbock (＠Patrick) Jan. 16, 2025

Jan. 16, 2025

On Sat Dec 7 21:33:25 2024 +0000, Rémi Bernon wrote: > I don't know for sure but there are probably some ways to make it work. > It works already more or less well with embedded systray windows, so > maybe doing something similar could be enough. > Alternatively mouse input is mapped in `map_event_coords` and we > preferred event root/x_root/y_root values when available because it > avoided some inconsistencies when moving windows, but window positioning > has been refactored lately, and maybe this isn't necessary anymore. > Using window-relative mouse input could solve your case too (or we could > also perhaps consider a winecfg option to prefer it over absolute positions). Hi Rémi. With the change below (bug51357.patch) from https://bugs.winehq.org/show_bug.cgi?id=51357 the wrong mouse offset is fixed in the VST plugin's main window titled 'Spire'. But, e.g. clicking the 'menu' button shows the menu in the wrong place. See screenshot. The menu should appear below the 'menu' button (top row) in the window titled 'Spire'. So the change above does not fix the issue but hopefully it gives you an idea what the problem might be. If you need more information please let me know. Thanks! [bug51357.patch](/uploads/dea8a1e711846f7e7642c16eacd284b4/bug51357.patch) ![Screenshot_From_2025-01-16_11-49-56](/uploads/decbb70d2abc1b99d3fd28e0b6382080/Screenshot_From_2025-01-16_11-49-56.png) -- https://gitlab.winehq.org/wine/wine/-/merge_requests/6569#note_92034

1 0

Re: [PATCH v3 0/0] MR7131: DIR command improvements: Make /o by itself behave equal to how it does in Windows
by eric pouech (＠epo) Jan. 16, 2025

Jan. 16, 2025

if you can start cmd.exe and notepad.exe from your installation, that should be sufficient to run the tests are you running the tests with winetest or make test? the later can sometimes have issues with some symlinks from the build directory. using the former is safer -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7131#note_92028

1 0

Re: [PATCH v2 0/1] MR7149: gdiplus: Check for MapFont result in generate_font_link_info. - approved
by Esme Povirk (＠madewokherd) Jan. 15, 2025

Jan. 15, 2025

This merge request was approved by Esme Povirk. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7149

1 0

Re: [PATCH v3 0/0] MR7131: DIR command improvements: Make /o by itself behave equal to how it does in Windows
by Joe Souza (＠JoeS209) Jan. 15, 2025

Jan. 15, 2025

OK, well, these tests appear to be practically a complete failure on my system. I'm receiving what appears to be an endless stream of lines like "Can't recognize 'temp.bat "Z:\\home\joe..." as an external command"..., etc. Admittedly, my wine build system is minimal; I do not have nearly all of the dependencies installed, but it was enough to build a basic wine installation including my changes to DIR. What I can probably do is make the changes to DIR as I think they should be, and either submit those changes or leave them here for someone else if they want to devote the time and effort into getting the tests to run. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7131#note_92010

1 0

Re: [PATCH v2 0/1] MR7149: gdiplus: Check for MapFont result in generate_font_link_info.
by Santino Mazza (＠tati) Jan. 15, 2025

Jan. 15, 2025

I tried to call GetStrCodePages on Windows with this character and it also returns a codepage of 0, so Wine is behaving correctly. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7149#note_92009

1 0

[PATCH v2 0/2] MR7148: Mark some debug formats as deprecated.
by eric pouech (＠epo) Jan. 15, 2025

Jan. 15, 2025

The aim of this MR is to mark some debug formats loaded by dbghelp as deprecated. The idea is to remove them from dbghelp: - after Wine 11 is released (for the ones still working) - during PDB rewrite landing (after Wine 10 is released) if this can help the process The considered debug formats are: 1) COFF inside PE images 2) CodeView inside PE images 3) OMAP inside PE images 4) split debug info in .DBG files 5) PDB (in JG format). This is an early format, which has been superseded by the DS format. clang only supports/understands the later DS format. I retested on a small 'Hello World' application, using a MSVC compiler from 1998 (version 12.0). This compiler allows to emit COFF in PE images, split .DBG and PDB/JG debug formats (it doesn't even seem to be able to emit Codeview inside PE images, nor OMAP). And from MSVC 14.0 onwards, none of these formats are available (only PDB DS). Test results with MSVC 12.0: - COFF inside PE image: doesn't work - split .DBG: doesn't work - PDB JG: does work (even if exceptions are caught) work = can set BP on main, can backtrace (with line number) when that BP is hit (using winedbg + builtin dbghelp) -- v2: dbghelp: Emit deprecation FIXME for embedded, .dbg and PDB JG formats. winedump: Use correct computation for first section out of a .DBG file. https://gitlab.winehq.org/wine/wine/-/merge_requests/7148

4 4

[PATCH 0/2] MR7148: Mark some debug formats as deprecated.
by eric pouech (＠epo) Jan. 15, 2025

Jan. 15, 2025

The aim of this MR is to mark some debug formats loaded by dbghelp as deprecated. The idea is to remove them from dbghelp: - after Wine 11 is released (for the ones still working) - during PDB rewrite landing (after Wine 10 is released) if this can help the process The considered debug formats are: 1) COFF inside PE images 2) CodeView inside PE images 3) OMAP inside PE images 4) split debug info in .DBG files 5) PDB (in JG format). This is an early format, which has been superseded by the DS format. clang only supports/understands the later DS format. I retested on a small 'Hello World' application, using a MSVC compiler from 1998 (version 12.0). This compiler allows to emit COFF in PE images, split .DBG and PDB/JG debug formats (it doesn't even seem to be able to emit Codeview inside PE images, nor OMAP). And from MSVC 14.0 onwards, none of these formats are available (only PDB DS). Test results with MSVC 12.0: - COFF inside PE image: doesn't work - split .DBG: doesn't work - PDB JG: does work (even if exceptions are caught) work = can set BP on main, can backtrace (with line number) when that BP is hit (using winedbg + builtin dbghelp) -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7148

4 5

Re: [PATCH v2 0/0] MR7131: DIR command improvements: Make /o by itself behave equal to how it does in Windows
by Joe Souza (＠JoeS209) Jan. 14, 2025

Jan. 14, 2025

About the multicriteria sort, there is clearly a hierarchy involved, and some options are mutually-exclusive (e.g DIR /O:SD on Windows 10 sorts by size, not time). Looking at the available options, it appears to me that G is the only one that can be combined, and with only one additional option. In the code, we probably need separate handling for N,E,S,D each by themselves, and separate handling for these combined with G. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7131#note_92002

1 0