On Mon, Feb 27, 2006 at 02:22:02PM +0100, Anselm R. Garbe wrote: > On Sun, Feb 26, 2006 at 02:27:02PM +1000, Chris Foster wrote: > > I've "fixed" the problem by hacking the aqsis source to remove the title > > update, but that's a little irritating. Does anyone know if this is a > > wmii problem, or just another a case of a broken app? Aqsis uses FLTK > > for the user interface... are there known problems with other FLTK apps? > > Would be interesting how wmii-current from hg tip performs without your hack, > because it is using libixp(2) and the ugly spawning events on > client-update have gone. The problem with frequently changing > titles applications is, that for each title update in wmii-2.5.x > around 3 processes are forked (two of them open old-style IXP connections). > Thus this is a bad bad bottleneck. Thus I recommend trying hg > tip if the issue is handled better by now.
I've finally had time to installed the latest snap (wmii-20060308) and I must say that I'm impressed by the new features. Some issues remain with the non-hacked version of aqsis however. Although it's far better than before, wmii still stops responding to keystrokes during the window title updates. Does a window title change get processed by the event loop in wmiirc? If so I guess I'm not surprised & I could see how using a faster interpreter than bash would fix the problem... Also: a quick comment on the stack layout. If I open a bunch of terminals in a stack, go to the "bottom" one and close it, I end up in the top terminal. This seems rather non-intuitive to me. I'd expect to end up in a terminal adjacent to the one I've just closed. (Actually, the same complaint applies to the equal layout as well.) As usual, thanks for the great work. ~Chris F. _______________________________________________ [email protected] mailing list http://wmii.de/cgi-bin/mailman/listinfo/wmii
