Ok, thanks. Waiting for pointer movement or for the pointer leaving the
workspace makes sense. But to check if a window is under the pointer
does not, does it? This piece of code also does not appear in the bug
report. When you close a window - the use case mentioned in the bug
report - with a mouse click, the pointer cannot be above a window
anyway... I refer to this snippet:
let actorUnderPointer =
global.stage.get_actor_at_pos(Clutter.PickMode.REACTIVE, x, y);
for (let i = 0; i < this._windows.length; i++) {
if (this._windows[i].actor == actorUnderPointer)
return GLib.SOURCE_CONTINUE;
}
I don't see any use case for that... which doesn't mean that there isn't
any.
On Thu, 2015-01-22 at 22:07 +0100, Florian Müllner wrote:
> On Thu, Jan 22, 2015 at 9:29 PM, Paul Neulinger <mailingl...@tanwald.net>
> wrote:
> > why is repositioning of windows delayed, when a window-actor is under
> > the pointer?
>
> The reason is mentioned in the commit message[0] and the referenced bug
> report.
>
> [0] https://git.gnome.org/browse/gnome-shell/commit?id=40b045917488504
_______________________________________________
gnome-shell-list mailing list
gnome-shell-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-shell-list
