[compiz] A few more bugs...

[Vasek Potocek]

>> 2) This one should be easily reproducible:
>> - Shade one window (W1) on a viewport.
>> - Click another window (W2) to move focus on it.
>> - Unshade W1 by double-clicking its title bar.
>> - Click W2 again - it gets focus, but graphically it still looks like W1 has it. Repeated clicking on W2 doesn't help.
> 
> Hm, I can't reproduce this but I fixed a shading focus issue just before
> I read this and it might very well be related to this issue. Please try
> again with the latest code and let me know if it's still broken.

Yes, it remains here... In git, I found that you have solved the mentioned issue in event.c, so I added some printf's 
there and here is what I get:

(W2 clicked)
FocusIn:  0x8876fd8  ID: 03E09243  Active: 03E07C26
FocusIn:  0x8876fd8  ID: 03E09243  Active: 03E09243
(W1 title bar double-clicked)
FocusIn:  0x8876978  ID: 03E08508  Active: 03E09243
FocusIn:  0x8876978  ID: 03E08508  Active: 03E08508
FocusIn:  0x8944108  Not managed
(W2 clicked)
FocusIn:  0x8876fd8  ID: 03E09243  Active: 03E08508
FocusIn:  0x8876fd8  ID: 03E09243  Active: 03E09243
(W1 title bar double-clicked)
FocusIn:  0x8944108  Not managed
FocusIn:  0x8944108  Not managed
(W2 clicked)
FocusIn:  0x8876fd8  ID: 03E09243  Active: 03E09243
FocusIn:  0x8876fd8  ID: 03E09243  Active: 03E09243

So, clicking the shaded window does not change d->activeWindow and compiz thinks the last window is still focused. I 
don't know all the code about, first of all, I don't know who then gives focus to W1, but I believe you will understand 
well what is going on here.

V.