(apologies for breaking threading)
Eckehard Berns wrote:
> Dwm does this by intention. In manage() in dwm.c the code explicitly
> checks, whether the new window is a transient for an already managed
> client. If so, the tags and monitor settings are copied from the main
> window (in your case the ooclac window already open).
Connor Lane Smith wrote:
> The problem is these damn "singleton" applications which insist on
> using the same window rather than separate ones for each process. As
> far as dwm is concerned one is claiming to be a transient window for
> the other, and it's handling the case correctly.
Thanks both for the explanation.
Eckehard, your suggested patch didn't work; seemingly the floating
window is never mapped to any tag at all. But I don't really want
to potentially break other applications just to make oocalc's
behaviour less obnoxious.
Connor Lane Smith wrote:
> Could you post the output of xprop for the two windows?
Attached (pwwinprop is the popped up enter password window,
existingwinprop is the already open oocalc).
This archive was generated by hypermail 2.2.0 : Wed Aug 10 2011 - 10:36:03 CEST