Comment 6 for bug 1073724

here are excerpts from my IRC conversation with Jasper re this bug.
----
<Jasper> darkxst, it's entirely possible that it will break it on monitor edges
<darkxst> the barrier_find_nearest() function definately breaks on the monitor edges when using the unclamped values
<Jasper> darkxst, I'm quite sure it will break BarrierNotify behavior, to be honest

<Jasper> I know exactly what the issue is: since we're using the unclamped positions, they're not clamped to the screen edges
<darkxst> if I hit the top edge I the screen it almost always slides past

<Jasper> darkxst, we have three pieces of information: where the mouse came from, where the mouse is going to unclamped to the screen edges, where the mouse is going to clamped to the screen edges
<Jasper> darkxst, between those three it should be possible to figure something out, but I can't figure anything out
<Jasper> darkxst, the issue that RAOF was talking about was what happens when clamped and where the mouse is coming from end up to be the same thing -- that is, when we're bumping against a barrier on the screen edge
<Jasper> so we switched to unclamped to allow for screen edges there
<Jasper> now what's happening is that the unclamped mouse position is outside the bounds of the monitor, which the barrier doesn't reach to, so it doesn't consider it blocked
<Jasper> darkxst, feel free to copy/paste this conversation onto the LP bug -- whatever solution RAOF comes up with is really interesting to me, because I'm turning his patches into a core X feature for 3.8.