On Mon Jun 22 09:08:30 2026 +0000, Rémi Bernon wrote:
Note that it could also be nicer to not wait for anything, and use NtUserCallNoParam_DisplayModeChanged when we've received the information to tell win32u about updated display devices. It may mean using default dummy display devices on prefix startup, which could perhaps have undesired effects, or perhaps not. Unfortunately, we do have to wait for all the globals to get registered at the least before we can proceed with the rest of the init code, and handling all the initial events is also required so that the wl_keyboard and wl_pointer exist before process init. I'm in favor of using a condition variable, though, and we can potentially put a timeout on it in case the compositor misbehaves.
Is the system thread stuff ready to be used on a driver like winewayland (can we use win32u with system threads)? I could add that into this patch as well if we are using a condition variable -- https://gitlab.winehq.org/wine/wine/-/merge_requests/11203#note_143824