<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Blender viewport "goes crazy" when mouse reaches viewport window edge in fly mode (Shift+F) or moving object (G)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=100740#c14">Comment # 14</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Blender viewport "goes crazy" when mouse reaches viewport window edge in fly mode (Shift+F) or moving object (G)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=100740">bug 100740</a>
from <span class="vcard"><a class="email" href="mailto:jadahl@gmail.com" title="Jonas Ådahl <jadahl@gmail.com>"> <span class="fn">Jonas Ådahl</span></a>
</span></b>
<pre>(In reply to Carlos Garnacho Parro from <a href="show_bug.cgi?id=100740#c13">comment #13</a>)
<span class="quote">> Nah I'm wrong. Blender seems to warp the pointer to the opposite side of the
> view in "move object" mode (pressing 'g'). Since xwayland warp emulator just
> kicks in when the pointer is hidden (and it's not the case), the warp gets
> ignored and Blender acts as if you were hitting the edge on every motion.
>
> I'm not sure how can this be fixed though... Even if we allow warping while
> the pointer is visible, according to the protocol we can't lock onto a
> region the pointer is not in. Jonas, any ideas?</span >
I think we might have discussed this on IRC (?) about warping after the cursor
is hidden, but FWIW, the protocol does allow warping a locked pointer, it just
requires the pointer to be within the lock region when locked.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>