[windows] window title shows "not responding" when loading a map

Bug #877710 reported by Hans Joachim Desserud
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
widelands
Fix Released
Medium
Unassigned

Bug Description

Steps to reproduce:
1. Run Windelands on Windows (in windowed mode, since you will not see the title in full screen).
2. Start a new game
3. While the game is loading, observe the window title.

On Windows (at least win7) the title will include "not responding" most of the time while the game is loading. Note that the game loads fine and everything works, it's only when the game is loading the title displays "not responding". I am not sure if the intense loading ignoring all user inpit makes the window unresponsive, so that the message is justified, but I fear that users (especially on slower systems) might think Widelands has frozen and won't complete loading. On the other hand I am not sure how much we can do to change this behaviour.

Oh, and I have not seen this on Ubuntu/other operating systems. But since that's a different OS, checking if a program is still responding or not, might be (and probably is) done in a different way.

Tags: windows
description: updated
Chuck Wilder (chuckw20)
Changed in widelands:
status: New → Confirmed
Revision history for this message
Chuck Wilder (chuckw20) wrote :

I encounter the same problem on my Windows Vista laptop. The Widelands screen freezes thereby apparently halting the load progress indicator as well as the OS adding "(not responding)" on the Widelands window bar.

It may not occur if you don't touch the mouse or keyboard during the Widelands load, but the moment I adjust the window position or click away to another window, the Widelands screen freezes and the message is displayed. The load progresses normally, but without looking at my harddrive activity light, there is no other indication Widelands is still working until the map window opens.

Revision history for this message
Shevonar (shevonar) wrote :

The problem was that events (like mouse press, key press, etc.) haven't been polled and handled during loading. I fixed it by polling the events but not handling them (just ignore the events). Events are polled at every step change (new text in progress bar). That might be not enough on slow systems, but the "not responding" should vanish at the next step. To further improve the situation events could be polled even more often, but I think it is not necessary.

Fixed in revision 6037.

Changed in widelands:
status: Confirmed → Fix Committed
importance: Undecided → Medium
milestone: none → build17-rc1
Revision history for this message
Chuck Wilder (chuckw20) wrote :

It sounds like you "nailed it". :) I am eager to try it out in the next Windows build from Tino.

Revision history for this message
SirVer (sirver) wrote :

Released in build17-rc1.

Changed in widelands:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.