Hello, On 14 July 2011 15:57, Frank Gruellich <fr...@der-frank.org> wrote: > I'm using the RaiseAndFocus function from the config I posted. I also > sometimes raise windows by clicking manually on their title or border.
No, but the focusing of that window might; see previous comments. > Can that mess up the window ring? Is there a way to dump the entire > ring, maybe without changing its order or the pointer into it? There is, but only as a debug-aid, it's nothing that's interactive, or would be of much use to you that I can tell. >> For what you want though, it sounds like you want to keep the window >> ring in the order they were created, rather than having them jumbled >> up through last focused? > > Yes, I think so. > >> If that's so you'll need to set the following: >> >> Style * !FPSortWindowlistByFocus > > That does not help. At some point it *sometimes* stops at a particular > window. Can you please do all you can to reliably reproduce this, including noting which clients are causing the problem? Note also, that this weird focus model will be reliant on things like: * Transient window policy (which can be told to steal focus); * UrgencyFunc * EWMHActiveWindowFunc All of these might have, during your testing, been a causal factor in messing up the results you expected. Hence: DestroyFunc UrgencyFunc DestroyFunc EWMHActivateWindowFunc > It's also hard to reproduce it, at least, I do not find a reliable > procedure to do that. Right now it works as expected, same > configuration. I don't know what I did wrong the last time. Well, keep an eye on it for me, and if you can come up with something more reliable, let me know. -- Thomas Adam