<div dir="ltr">To be more clear, "interactive moving" being a separate protocol is actually how it works under X11 too. To begin interactively moving the window, clients send a _NET_WM_MOVERESIZE ClientMessage [0] to the window manager which handles moving for it. We adapted the same protocol for xdg_surface in Wayland.<br>
<br>[0] <a href="http://standards.freedesktop.org/wm-spec/wm-spec-latest.html#idm140146176808576">http://standards.freedesktop.org/wm-spec/wm-spec-latest.html#idm140146176808576</a><br></div><div class="gmail_extra"><br><br>
<div class="gmail_quote">On Mon, Aug 11, 2014 at 6:57 AM, Giulio Camuffo <span dir="ltr"><<a href="mailto:giuliocamuffo@gmail.com" target="_blank">giuliocamuffo@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
2014-08-11 13:29 GMT+03:00 Rutledge Shawn <<a href="mailto:Shawn.Rutledge@digia.com">Shawn.Rutledge@digia.com</a>>:<br>
<div class="">><br>
> On 11 Aug 2014, at 11:34 AM, Giulio Camuffo wrote:<br>
><br>
>> 2014-08-11 12:20 GMT+03:00 Rutledge Shawn <<a href="mailto:Shawn.Rutledge@digia.com">Shawn.Rutledge@digia.com</a>>:<br>
>>><br>
>>> On 11 Aug 2014, at 9:10 AM, Pier Luigi wrote:<br>
>>> (top-posting fixed)<br>
>>>> 2014-08-11 8:13 GMT+02:00 Steve (YiLiang) Zhou <<a href="mailto:szhou@telecomsys.com">szhou@telecomsys.com</a>>:<br>
>>>>> Dear all,<br>
>>>>><br>
>>>>> My app has a mainwindow and a QDialog which is a child of mainwindow. And I<br>
>>>>> want to set the app to the position 0,0.<br>
>>>>><br>
>>>>> I use both setGeometry and move to  0,0. No luck , both failed. The window’s<br>
>>>>> position is unfixed and may appear to anywhere on the screen.<br>
>>><br>
>>> I was wondering about that too. Â I understand that it's generally good policy to leave positioning of generic windows up to the window manager, but sometimes you want to write a dock or taskbar which anchors itself to screen edges, and can animate in and out of view; or a splash screen which is centered on one screen. Â What is the right way to do that on Wayland?<br>
>><br>
>> The right way is to have a protocol designed for that. A taskbar<br>
>> should use some taskbar_protocol with a request like<br>
>> put_on_edge(edge), and the compositor will then move the surface on<br>
>> the edge and do slide in/out or whatever effect it wants to.<br>
><br>
</div>> I understand the advantage of taking a higher-level approach. Â But then someone thinks of something for which the scenario-specific protocol doesn't suffice. Â If windows could move themselves, it might be more flexible. Â It may be too low-level, but it's hard to think of any other protocol that is universal enough, which I suppose is why it's not standardized.<br>
<br>
The problem is that windows don't always have a meaningful position.<br>
If a window is shown on two outputs at the same time, maybe one of<br>
which a remote one, what is the window position? And what is the<br>
position of a window rotated 45 degrees?<br>
<br>
><br>
> What about when a window provides its own "skinned" window decorations: there will probably be some area in which you can drag to move the window, as you normally can on the titlebar. Â Is there another protocol for that? Â How would that be different from a generic protocol which windows could use to position themselves?<br>
<br>
wl_shell_surface/xdg_surface have a "move" request. The clients call<br>
that and then the compositor actually does the moving.<br>
<div class="HOEnZb"><div class="h5">_______________________________________________<br>
wayland-devel mailing list<br>
<a href="mailto:wayland-devel@lists.freedesktop.org">wayland-devel@lists.freedesktop.org</a><br>
<a href="http://lists.freedesktop.org/mailman/listinfo/wayland-devel" target="_blank">http://lists.freedesktop.org/mailman/listinfo/wayland-devel</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Â Jasper<br>
</div>