URL:
<http://gna.org/bugs/?14550>
Summary: needs_select for menu item does not work after
moving selected unit
Project: Battle for Wesnoth
Submitted by: sapient
Submitted on: Sunday 10/18/2009 at 03:46
Category: Bug
Severity: 3 - Normal
Priority: 7 - High
Item Group: WML
Status: None
Privacy: Public
Assigned to: None
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: 1.7
Operating System: all
_______________________________________________________
Details:
as described here:
http://www.wesnoth.org/forum/viewtopic.php?p=389468#p389468
When you move the unit and cannot undo the movement, then the "moveto" event
has already been sent and synchronized on all clients.
Next, you use the menu item and then the game realizes it needs to sync that
last "select" event as well, before it fires the menu item.
But it is already too late to send the last select event, because it would be
sent out of order.
So this is a limitation of needs_select. :(
I can only think of one idea to fix it... The game may be able to send a
select event at the new location of the unit, but this assumes two things: 1)
that the unit wasn't killed since the time it was selected. And 2) that
processing the select out of order with the moveto would not pose a concern.
Probably, the engine should fire a new select event on the originating client
at this new location *before* processing the menu item [command] block, so
that the behavior of needs_select would be similar on all clients. Also, to
alleviate problem #1, the game could hide all needs_select menu items if the
last selected unit has been killed or removed from the gamemap.
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?14550>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Wesnoth-bugs mailing list
Wesnoth-bugs@gna.org
https://mail.gna.org/listinfo/wesnoth-bugs
