On 2012-03-04 01:36:46, Juan Francisco Cantero Hurtado <i...@juanfra.info> wrote: >On Sat, 03 Mar 2012 04:56:29 +0100, Bryan Linton <b...@shoshoni.info> wrote: >>On 2012-03-02 16:19:38, David Coppa <dco...@gmail.com> wrote: >>> >>>http://pbot.rmdir.de/fa0e34c8bfab313978f7f9088ce30e8c >>> >>>Thanks for the tip, >>>David >>> >> >>I tested it for about 5 minutes before having to roll back to >>0.92.0. The problems I saw were as follows. >> >>Trying to set ports/games/wesnoth to full-screen mode via its >>in-game option started a weird loop where the screen would >>continuously resize from 1600x1200 (my default) to 1024x768 (how >>I've set Wesnoth's full-screen mode) and then back to 1600x1200 (and >>then to 1024x768 etc.). >> >> [...] >> >>I've had no problems switching from windowed to full-screen mode >>before. It's always seamlessly changed to full-screen mode and the >>lower resolution and then back again with no problems. >> > > Comment the line with "--enable-xrandr" in the makefile and try > again. This is a new option and can be the culprit. >
This seems to have fixed the problem. Also, I noticed that the problem I had with the double spawning of xterms when I press ctrl+u is fixed as well. I wonder if this behavior was a bug triggered by the resize loop because I can't reproduce it now. I also can't remember if it was double-spawning before I tried to launch Wesnoth or only after. Windows still "roll" up and down with an animation even though I have animations disabled in my preferences but this is only a minor annoyance and something that I assume will be fixed in a future update of WindowMaker. So far it seems like everything else is working smoothly. I'll run with this new version since the show-stopping bugs are gone now and report back if anything major happens. Otherwise, if xrandr support were disabled (which on WindowMaker's website is admitted to needing more work to be bug free) it would be nice to see this committed. I've been running WindowMaker for 10 years now and it really is great that development is being picked up again. -- Bryan