Henri Verbeet hverbeet@gmail.com writes:
On 2 November 2015 at 22:46, Ken Thomases ken@codeweavers.com wrote:
As to why a year and a half isn't enough time to fix it: when velocity is 0, distance traveled is going to be 0 regardless of time. I'm no longer working on the proper fix. Let's chalk it up to emotional immaturity on my part. If that makes you reluctant to have my work in wined3d, then you have a sticky dilemma to resolve. ;)
I have my own theory, but regardless of who or what you blame it on, it does indeed make me more hesitant to sign off on your changes, nothing sticky about that.
It doesn't matter who's to blame, the fact is that we won't get the proper fix for 1.8, so what I'd like to hear is your opinion on whether it's better to revert the change or ship 1.8 with that regression.