https://bugs.winehq.org/show_bug.cgi?id=49423
Sveinar Søpler cybermax@dexter.no changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |cybermax@dexter.no
--- Comment #6 from Sveinar Søpler cybermax@dexter.no --- (In reply to Zebediah Figura from comment #4)
(In reply to Bloody Iron from comment #3)
How does testing with WINE 5.7 not constitute a rough regression test? I tested with WINE 5.7 today and confirmed the issue.
By "regression test" we refer to a bisect, to determine exactly which commit causes this bug.
It is somewhat impossible to do regression testing between releases for "normal people". Especially when talking about difference from 4.16 -> 5.7 if that is the case.
Is there a different way to log what might be causing "input lag"?
Lets pretend that a user just complains about perceived input lag coming from Windows without ever having used prior wine versions... How would one try to figure out what was happening instead of bisecting possible thousands of commits.