Window focus is not transferred properly sometimes. I am using the "Focus
windows when the mouse pointer moves over them" setting in ObConf.
The problem only seems to occur when the computer is using lots of CPU, like a
compile or decompression and lots of disk access. It almost always happens when
moving the mouse from an application with lots of graphics or otherwise complex
appearance, in my case Mozilla Firebird. I move my mouse pointer from Mozilla to
another window and then to the destination window (usually an xterm) and this
destination window (xterm) will not receive focus. I have to move the mouse out
of the window and back over it.
This happens in both 3.0, 3.1 and CVS as of January 3rd 2004 12:00 GMT
(approx.). I compiled the CVS version with DEBUG and DEBUG_FOCUS defined. The
regular output from focusing a window did not appear at all, not even the part
about the event notification that usually comes first.
The easiest way to reproduce this bug (for me) is to start something CPU/disk
intensive, compiling usually and then have Mozilla and two xterms started. I
then move my mouse across all three windows starting with xterm #1 moving to
Mozilla and then to xterm #2. If I move the mouse quickly enough or Mozilla is
slow enough in losing its focus xterm #2 won't receive focus.
Visually it looks like Mozilla does not receive focus or release focus before I
have entered the second xterm.
I would be happy to assist in any other way, just tell me how.
I don't even need high load, or "fat" windows to reproduce this. Three xterms
suffice. I found a way to reproduce this, though it's a bit tricky. I'll try
some ASCII art to explain:
Start three xterms, place them like this.
|
-----------| x1
| |__________
| x2 ___|____
| |
| | x3
|__________|
|
|________
The space between x1 and x3 needs to be small, not very small, but also not too
big. Now place the cursor in X1, make sure it is activ. You now have to do a
circle x1 - x2 - x3 - x1, rather quickly. Always make sure that x1 has focus
when you start. Try various speeds, you will notice, that after the end of the
circle x1-x2-x3-x1, x2 will have the focus, and NOT x1.
I hope this helps in reproducing this bug. Btw, this bug might be related to
#952 and #908.
i can't make this happen anymore.
i think bug #908 is fixed, and i think as a result, this is also.
let me know if otherwise! :)
*** This bug has been marked as a duplicate of bug 908 ***
I don't even need high load, or "fat" windows to reproduce this. Three xterms suffice. I found a way to reproduce this, though it's a bit tricky. I'll try some ASCII art to explain: Start three xterms, place them like this. | -----------| x1 | |__________ | x2 ___|____ | | | | x3 |__________| | |________ The space between x1 and x3 needs to be small, not very small, but also not too big. Now place the cursor in X1, make sure it is activ. You now have to do a circle x1 - x2 - x3 - x1, rather quickly. Always make sure that x1 has focus when you start. Try various speeds, you will notice, that after the end of the circle x1-x2-x3-x1, x2 will have the focus, and NOT x1. I hope this helps in reproducing this bug. Btw, this bug might be related to #952 and #908.