<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Jul 18, 2014 at 2:26 PM, Bill Spitzak <span dir="ltr"><<a href="mailto:spitzak@gmail.com" target="_blank">spitzak@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On 07/18/2014 09:55 AM, Jason Ekstrand wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I really like Jasper's "present" request solution to this problem. (It<br>
could probably also be called "attention"). If kwin wants to implement<br>
that as "move to the appropriate workspace and unminimize, then it can<br>
do that. Otherwise, it could start flashing the task-bar icon or something.<br>
</blockquote>
<br></div>
I see no reason this can't be called "show" or "raise".<br>
<br>
The *creation* of a surface does not mean that the compositor must show it. It could add a blinking "attention needed" task bar entry, just like this action. And the Kate editor is actually expecting "the same result as a new window", not "the window becomes visible". Therefore the request that is really wanted is "do something much like what happens when a window is first created".<br>
</blockquote><div><br></div><div>That's not true. If Kate destroyed and recreated the window, the window would suddenly appear on a different workspace. In the existing case, Kwin immediately switches to the workspace of the window.<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I would add an event id to the request, so the compositor knows what event (if any) triggered it. This same request would be used in several situations, and the event and whether the window is visible can be used by the compositor to change the result:<br>
</blockquote><div><br></div><div>I have no idea what an "event ID" even is. We could add a timestamp or a serial, and that's something we've discussed doing.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
1. It is implied when a surface is first created.<br>
<br>
2. Clients use it to raise windows on clicks (note: the compositor CANNOT implement "raise on click" itself. If you think it can you are wrong).<br></blockquote><div><br></div><div>Please stop derailing the thread with unrelated topics.<br>
</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
3. Clients use it in response to other actions, as in the Kate editor above.<br>
<br>
Compositors must cleanly and quickly ignore spurious requests, as some clients may send them in response to every click, or send extra ones after creating a surface.<div class="HOEnZb"><div class="h5"><br>
______________________________<u></u>_________________<br>
wayland-devel mailing list<br>
<a href="mailto:wayland-devel@lists.freedesktop.org" target="_blank">wayland-devel@lists.<u></u>freedesktop.org</a><br>
<a href="http://lists.freedesktop.org/mailman/listinfo/wayland-devel" target="_blank">http://lists.freedesktop.org/<u></u>mailman/listinfo/wayland-devel</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br> Jasper<br>
</div></div>