selcolors drawn on unfocused frame

[GoogleCodeExporter]

What steps will reproduce the problem?
1. On a new view, open two GTK programs (such as gcalctool or firefox)
2. Move one of the clients to the right (thereby creating a new column)
3. Focus the left client and observe that both clients' frames are now
drawn with selcolors.
4. Any subsequent focus changes (moving the focus to the left/right column)
will draw the selcolors only on the focused frame.

What is the expected output? What do you see instead?

Both clients should not have selcolors, only the left client should.

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

$ wmii -v
wmii-hg2308+, ©2007 Kris Maglione

$ uname -a
Linux yantram 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686
GNU/Linux

Please provide any additional information below.

I have only observed this with GTK apps.

Original issue reported on code.google.com by sun...@gmail.com on 17 May 2008 at 2:22

[GoogleCodeExporter]

I can confirm this. But for me, this only occurs when mixing the "selection 
method",
i.e., using the mouse, or the keyboard.

For further clarification on how to reproduce the bug:

1. Create new view
2. Open at least one GTK application (e.g., gvim)
3. Move the GTK client to the right (new column)
4. Select the GTK client using the mouse (re-select, since it's probably already
selected)
5. Now select the other client using the keyboard (e.g., M^h)
6. Both client will be seen as focused

When reading the event, it seems that the GTK clients sometime gets focused 
twice
when they're focused using the mouse. But I'm not sure... just a hint :)

Original comment by a.pon...@gmail.com on 18 May 2008 at 12:35

[GoogleCodeExporter]

This is a dup of #10, and should be fixed in 2309:35f1fda4ead2.

Original comment by maglion...@gmail.com on 18 May 2008 at 5:34

• Changed state: Fixed
• Added labels: Component-WindowManager, Priority-Critical
• Removed labels: Priority-Medium

[GoogleCodeExporter]

I confirm that this issue is fixed in 2309:35f1fda4ead2.  Thanks!

Original comment by sun...@gmail.com on 18 May 2008 at 5:49