Originally posted by gggeek
View Post
Originally posted by ⲣⲂaggins
View Post
What was fixed in mutter 42 is that mutter held back delivery of mouse input events until the next time it worked on an output frame. This meant that mouse input events were only sent out at the display refresh rate and could get delayed by up to one display refresh cycle (16.6... ms at 60 Hz). As a result, running mouse-controlled games at frame rates higher than the display refresh rate was mostly pointless.
Event compression in GTK just means that if multiple events have arrived by the time the application processes them, they are compressed and reported as if there was only a single event resulting in the same final state. This does not result in events getting delayed; it makes no functional difference for the vast majority of applications, and saves event processing CPU cycles for them. That's why it's the sane default. Per the text you quoted, the minority of applications which do want all individual events (e.g. painting apps) can get them via gdk_event_get_history.
Comment