On Sat, 03 Mar 2012 04:56:29 +0100, Bryan Linton <
bl@...> wrote:
> On 2012-03-02 16:19:38, David Coppa <
dcoppa@...> 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.).
>
> It took about a second or two between switches. The first time it
> happened I was quick (or lucky) enough to untick the full-screen
> checkbox and the screen went back to 1600x1200. The second time
> I ended up switching to a console terminal and pkilling wesnoth.
> The screen was left in 1024x768 mode and had to be set back to
> normal via xrandr.
>
> 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.
>
> Another issue is that I have ctrl+u mapped to spawn an xterm. In
> 0.95.2 a single press of ctrl+u would open two xterms instead of a
> single one.
>
>
> One final issue I saw was that despite the fact that I have all
> animations turned off in WindowMaker's preferences app,
> double-clicking window titles "rolled" the window up and down
> smoothly instead of instantly {dis,re}appearing.
>
> I'm very happy to see WindowMaker getting active development and
> that you've taken the time to update the port, but with the
> full-screen bug and the double-spawning of xterms I was not able
> to use the new version and had to roll back to 0.92.
>
> If there's any more information I can provide to help, I would
> very much like to see an updated version of WindowMaker in the
> ports tree.
>
> All packages are up-to-date with regards to the snapshot I'm
> running.
>
> dmesg follows. (I know it's a bit old and does not have the rthread
> changes. I've been waiting for a new snapshot to be released. I
> can retest as soon as a new snap is released if you think it will
> make a difference.)
>
--
Juan Francisco Cantero Hurtado
http://juanfra.info