Comment 2 for bug 1073724

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.