March 17, 2026
2:29 p.m.
http://bugs.winehq.org/show_bug.cgi?id=57980 --- Comment #13 from Qwerty Chouskie <asdfghrbljzmkd@outlook.com> --- Hmm, it looks like a DWORD can't be null, so that extra check is unnecessary. (Then why do the docs specify `[in] DWORD msWindowLength` for SetThreadpoolTimer and `[in, optional] DWORD msWindowLength` for SetThreadpoolTimerEx? Maybe just docs being inconsistent...) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.