New windows appear on unexpected screen for apps that spawn new windows using existing processes

[GoogleCodeExporter]

These steps require a multihead (Xinerama) setup and are all done on a
single group.

1. Move focus to screen 0 and run "firefox". 
2. A new Firefox window appears on screen 0.
3. Move focus to screen 1 and run "firefox". 
4. A new Firefox window appears on screen 0. Expected the window to appear
on screen 1.

This behaviour isn't specific to Firefox. It happens with any app
that creates new windows belonging to the same process when new
instances are started (Thunderbird, Google Chrome, Emacs etc).

Windows only appear on the current screen if there is no other
window belonging to the application in existance.

What version of the product are you using (wmii -v)? On what operating
system?

wmii-hg2600, ©2009 Kris Maglione
Suse SLED11.

I'm happy to test patches or provide further information if required.

Original issue reported on code.google.com by menno.sm...@gmail.com on 8 Apr 2010 at 10:15

[GoogleCodeExporter]

This has been a known feature ;-) for a loooong time.  You can workaround this 
by 
listening for the CreateClient event and adding the current view's tag to the 
client.

See also http://github.com/sunaku/wmiirc/blob/master/display/client.yaml#L34

Original comment by sun...@gmail.com on 12 Apr 2010 at 9:01

• Changed state: Accepted

[GoogleCodeExporter]

Aren't these two different things?
The workaround by sunaku is for the tagging problem also mentioned in issue 165 
and
fixed by Kris.
What menno.smits describes happens on a single tag with two screens. So I cannot
imagine that a tagrule "/Firefox/ -> sel" or sunakus workaround fixes this 
issue, but
maybe it is worth a try.

Original comment by skwi...@googlemail.com on 28 Apr 2010 at 6:42

[GoogleCodeExporter]

I confirm this issue (using acroread) and that it is different from issue 165, 
i.e.,
tagruling acroread sel does not help. Did not test with sunaku's wmiirc though.

I can see uses for the current behavior, so in the end the ability to add a 
screen
preference by a tagrule would be nice:
- No tagrule: screen, where other windows of the application are (current 
behavior).
- tagrule "screen:0": first screen, etc.
- tagrule "screen:sel": the current screen
Maybe the last is problematic, one could argue that it should be ignored when 
the
client spawns on another but the current tag.

Original comment by skwi...@googlemail.com on 7 May 2010 at 12:09

[GoogleCodeExporter]

Apps in the same window group tend to open in the same column. At any rate, 
you're
right, I really need to extend tagrules.

Original comment by maglion...@gmail.com on 30 May 2010 at 7:51

[GoogleCodeExporter]

This issue was updated by revision 5a37afb525.

If you don't want grouping behavior for a client, set group=0 for
that client in /rules. This will inhibit the affinity for tags and
for columns.

Original comment by maglion...@gmail.com on 2 Jun 2010 at 2:39

• Changed state: Fixed