Passing in the unclamped x,y values to barrier_find_nearest(), fails to find nearest blocking barrier in some cases. Since we are measuring distance and not velocity I think its fine to use the clamped values in *x,*y, as per my patch in the linked branch. This fixes the issues in gnome-shell and does not appear to have any adverse affects in Unity.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073724 Title: Pointer barriers have gaps along the edge of the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1073724/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
