<div dir="ltr">On Thu, Oct 6, 2011 at 10:17, <span dir="ltr"><<a href="mailto:wagnerdm@seas.upenn.edu">wagnerdm@seas.upenn.edu</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">Quoting Troels Henriksen <<a href="mailto:athas@sigkill.dk" target="_blank">athas@sigkill.dk</a>>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<a href="mailto:wagnerdm@seas.upenn.edu" target="_blank">wagnerdm@seas.upenn.edu</a> writes:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
That strategy doesn't work when the layout of all the windows changes,<br>
since a window cannot be mapped at two places (and, potentially,<br>
sizes!) at once.<br>
</blockquote>
<br>
You could dump the contents of the workspace region to a pixmap, render<br>
that pixmap to a new (unmanaged) window covering the entire workspace,<br>
perform window movement/mapping behind it and unmap the covering window<br>
at the end. This would work, but it's ugly and complex. I doubt a<br>
simple and robust solution to this aesthetic issue can be conceived.<br>
</blockquote>
<br></div>
Cute. The generalization of this idea leads directly to a simple, robust solution: never unmap clients, and using OpenGL compositing to hide them instead. ;-)<br></blockquote><div><br></div><div>It's worth noting that a number of desktop environments *have* moved to OpenGL for window management; I don't know if they use compositing per se, but windows are often implemented as OpenGL textures so they can be manipulated this way. </div>
</div><div><br></div>-- <br>brandon s allbery <a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a><br>wandering unix systems administrator (available) (412) 475-9364 vm/sms<br>
<br>
</div>