> |Changing the SetInputFocus() to
> |"$xServer->SetInputFocus($winId, 'Parent', 'CurrentTime');"
> |its all working flawless.
> |
> |The variables in $tabWin{$tId}{focusTimestamp} does look ok though, but
> |i dont have any knowledge about the X11-Protocol. Perhaps you know
> |what could be wrong.
> Hi, I have the same problem with fvwmtabs 2.6,
> and I patched the line you're talking about,
> it works wonderfully.
Yes, this hack will fix your problem but it introduces another - focussing
race conditions. Early versions of FvwmTabs used 'CurrentTime' just as
you have, but in sloppy-focus modes tab-managers were stealing the
focus unnecessarily (extremely annoying when you pass the mouse cursor
over a tab-manager to get to another window! Although I can appreciate
that not focussing at all must be even more annoying!) I've been trying to
fix this bug for some time. Unfortunately I can't reproduce it on any of the
several different systems I have available to me.
I need to investigate further but its not going to be anytime soon. I'm
having
a miserable week - both my home & work systems crashed (independantly)
in the last few days & I've lost a sh*t-load of work ... :( ... I back-up
data
from home system to my work system & vice-versa so the double-failure
is killing me. How unlucky can you get?
Anyway, I didn't realise anyone else had this bug (I thought it was only
Tobias (I think - I can't access my email to check)). What system are you
using?
SCoTT.
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Mon Feb 23 2004 - 06:04:33 GMT