Follow-up Comment #4, bug #19734 (project wesnoth):
I only noticed this behavior while moving groups of units far from the
fighting. As I mentioned below, the previous unit usually finishes moving
before I issue the next order, allowing me to "stack" movement commands with
movement decisions and spend as little time on routine (and boring) troop
movements as possible. Not allowing them to "stack" could effectively double
the amount of time I spend shuffling troops down the road.
But the proposed delay would adversely affect even precision placement. The
difficult (time-consuming) part is deciding where to move. Once that decision
is made, I am already focusing on the next "difficult" move before the prior
unit finishes moving. In this case, though, I am unlikely to decide where to
move fast enough to experience the odd behavior I originally reported, but I
would definitely notice (and be annoyed by) the inability to select the next
unit and begin considering my moves.
If adding more delay is the recommended fix, I believe I prefer the current
implementation despite the occasional irritation.
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?19734>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Wesnoth-bugs mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-bugs
