> The problem seems to come about because the process of a window
> showing up is that we get a map request for it, so HandleMapRequest()
> calls AddWindow(), which does all the above and sets everything right.
> And then it overrides that priority with whatever EwmhGetPriority()
> wants to give the window, which is pretty much always 0. So it's
> actually fallout from the EWMH additions.
That makes a lot of sense. What does the EWMH priority info look like?
I mean, how compatible is it with ctwm's OTP? We can probably ignore it
if it's set to 0 (i.e. only obey EWMH if it's set to a non-default.
Stefan
