On Fri Jun 19 07:57:40 2026 +0000, Rémi Bernon wrote:
I mean, it's probably fine either way, my comment is actually more related to the other comment where I suggested to use a list directly in user thread info, which would make this mouse pointer allocation a bit out of place. But I suppose it also be done lazily, or with a static struct pointer returned from find_pointerid if id is 1. next set of patches will fill in the pointer struct as we get mouse messages (for GetPointerInfo w/ MouseInPointer)
a static pointerid would need to be per-thread i think, since pointer info is per-thread, though i suppose it can go directly into user_thread_info? alongside the `struct list` -- https://gitlab.winehq.org/wine/wine/-/merge_requests/11171#note_143631