3 ms·
There are a lot of ways for mouse input to be annoying for a particular OS / user. The bug described by the article, though, is not an area of "preference." T
by feralchimp 15y ago
There are a lot of ways for mouse input to be annoying for a particular OS / user. The bug described by the article, though, is not an area of "preference." The article claims that every device input to the mousing system takes [an extra? at least?] 32ms to be reflected in the state of the window manager.
To the question of whether it's "noticeable" or not, it'd be cool if someone wrote a driver or extension to intentionally add some additional lag. So even if we couldn't tell whether 15ms felt "snappier" than 32ms, we could at least report on whether 64ms feels "floatier" than 32ms, for example.
Not totally surprising that QuartzExtreme was mentioned. Flowing everything through a resolution-independence engine (right?) doesn't sound like it'd be free, even with fast procs and graphics cards.
- tikhonj 15y agoThe problem with just adding more delay to see if it would make a difference is that the way you feel the delay is likely nonlinear.
- feralchimp 15y agoGreat point. Per my example above, we might only discover that "64ms kinda sucks", not that "an additional 32ms on top of the original 32ms kinda sucks". And who knows, maybe after a "kinda sucky valley" there's some comfy-feeling region up above 250ms, where the "float" just feels okay. :)