On Wed, Aug 10, 2011 at 03:52:39PM +0100, Connor Lane Smith wrote:
On 10 August 2011 09:26, Nick suckless-...@njw.me.uk wrote:
Attached (pwwinprop is the popped up enter password window,
existingwinprop is the already open oocalc).
Bad news! Assuming existingwin is XID 0x28d, there is
(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
On Wed, Aug 10, 2011 at 03:52:39PM +0100, Connor Lane Smith wrote:
Bad news! Assuming existingwin is XID 0x28d, there is nothing in
pwwin's xprops to suggest that it should be treated in any other way.
Which means the only solution would be a hack like the one attached
(untested).
Yes,
Firstly: OpenOffice - I know. I currently have to use it a
little bit for work.
Now, on to the point.
* I have oocalc in tag 1
* I have tag 2 active
* I open a new oocalc, with a password-protected file
PROBLEM: the enter password floating window is opened in
tag 1 (as it's associated with
On Tue, Aug 09, 2011 at 04:32:52PM +0100, Nick wrote:
* I have oocalc in tag 1
* I have tag 2 active
* I open a new oocalc, with a password-protected file
PROBLEM: the enter password floating window is opened in
tag 1 (as it's associated with the original oocalc, I
suppose.)
Now, it
Hey,
On 9 August 2011 16:32, Nick suckless-...@njw.me.uk wrote:
* I open a new oocalc, with a password-protected file
PROBLEM: the enter password floating window is opened in
tag 1 (as it's associated with the original oocalc, I
suppose.)
The problem is these damn singleton applications
