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. -- 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
