Soldier's list updating too slow in miltary buildings

Bug #536249 reported by astuur
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
widelands
Fix Released
Low
Unassigned

Bug Description

When you expell soldiers from military sites, you sometimes get not the soldier you clicked on.
I had long been thinking it was me aiming badly, but its not so :)
Especially when you use the sorting feature (for skill points) and kick more than one in a row, it seems that the display has not updated yet.
So what you kick is not what you see.

Tags: military ui

Related branches

tags: added: military ui
Changed in widelands:
status: New → Confirmed
importance: Undecided → Low
Revision history for this message
Nicolai Hähnle (nha) wrote :

I'm not sure that I'm seeing exactly the problem you are describing; in particular, you definitely always kick the soldier that was selected, but I also noticed that the selection in the soldier list doesn't get properly maintained when the list of soldiers changes.

I've cleaned up that code in my branch lp:~nha/widelands/refactor-building-ui to fix the issue I am seeing - could you please try whether this also fixes your problem? If it doesn't, could you please describe more accurately what goes wrong in your opinion? Ideally with a save game plus a short list of steps to reproduce the problem.

Changed in widelands:
status: Confirmed → In Progress
Revision history for this message
Astuur (wolfsteinmetz) wrote :

I guess you most likely have found the cause.
I simply made sure I marked untrained soldiers before I kicked them,
and found that the result when doing so quickly and repeatedly,
was not as expected (from the badges above their heads)
I also saw that the sorted list seemed to change order while I was trying to mark the next one.
It looked like updating the order when some soldiers were leaving and others coming in,
was slow and sometimes led to unpredictable results
So it may well be a problem of marking the correct soldier after all.
I have not seen this particular thing in some time and cannot now supply a save game
that shows the bug - sorry.
I will gladly check this again when I come across a precompiled version that includes your fix.
( I have no develoment environment and no knowledge to compile myself)
Thanks for working on this

Revision history for this message
Nicolai Hähnle (nha) wrote :

I've committed my changes to trunk now, I'm assuming they fix your problem. If not, please let us know.

Changed in widelands:
status: In Progress → Fix Committed
Nasenbaer (nasenbaer)
Changed in widelands:
milestone: none → build16-rc1
Revision history for this message
SirVer (sirver) wrote :

Released in build16-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.