2009/1/27 Alexander Burger <a...@software-lab.de>: > Hi Thomas, > >> The same thing happens with Firefox from time to time. I don't see >> how this is a FVWM issue though -- mostly it happens with odd clients. > > Still, I'm wondering how this is possible ... Do these "odd" clients > grab the focus? How can they do, as they are already closed?
It's not that as such. Some applications have problems with input focus -- Mozilla (not so much Firefox, but I have seen this same problem from time to time) had this issue whereby if a textarea field were present, it would steal keyboard focus until the mouse had subsequently left the window and re-entered it --- but that's not FVWM's fault. To humour me, would you try: Style * FPClickDecorToFocus, MouseFocus, FPClickToFocus To see if this solves your issue? To explain, in the past where things like complex functions are run (i.e. UrgencyFunc, or the *abominal* EWMHActivateWindowFunc) which steal focus, if the mouse is grabbed at that point, or if you happen to be pressing the mouse button, then trying to focus that window by clicking in it might not always focus that application. (I think this is right -- hopefully someone will correct me on this if not!) This is what I can tell from looking at the code anyway -- try it, see if it works. I do wonder though why you're seeing it with XTerm --- that's certainly not my case. Alas, from looking at Voss' FVWM config, nothing he has defined there is likely going to help you. -- Thomas Adam
