GNOME Bugzilla – Bug 725103
evdev: Set the initial core pointer coordinates to a sane value
Last modified: 2014-02-27 10:58:24 UTC
This avoids the possibility of the pointer wandering outside the stage until it enters for the first time, after which mutter's constraint callback starts working.
Created attachment 270196 [details] [review] evdev: Set the initial core pointer coordinates to a sane value ClutterInputDevice's default initial coordinates is (-1, -1) and since they're updated from events in a relative way it means that the pointer can go outside the stage right from the first event. We usually let this up to higher layers to fix through the pointer constraint callback but that doesn't work if the first event doesn't put the pointer immediately inside the stage.
Review of attachment 270196 [details] [review]: looks okay to me. the (16,16) coordinates are a bit arbitrary: maybe a comment above their #define would be nice, but it's not, strictly speaking, necessary.
Pushed with a comment about the values. Attachment 270196 [details] pushed as 458de11 - evdev: Set the initial core pointer coordinates to a sane value