[Freeciv-Dev] [patch #3721] Getting rid of move_type dependency on unitselect dialog

Update of patch #3721 (project freeciv): Assigned to: jtn => None Planned Release:2.6.0, 3.0.0 => 3.0.0 ___ Follow-up Comment #7: Unit select

[Freeciv-Dev] [patch #3721] Getting rid of move_type dependency on unitselect dialog

Update of patch #3721 (project freeciv): Planned Release: 2.6.0 => 2.6.0, 3.0.0 ___ Reply to this item at: ___ Message

[Freeciv-Dev] [patch #3721] Getting rid of move_type dependency on unitselect dialog

Update of patch #3721 (project freeciv): Planned Release: 2.5.0 = 2.6.0 ___ Reply to this item at: http://gna.org/patch/?3721 ___ Message sent

[Freeciv-Dev] [patch #3721] Getting rid of move_type dependency on unitselect dialog

Follow-up Comment #6, patch #3721 (project freeciv): One of the patches in patch #4866 provides a new ruleset field (unit class group) that could be used for this purpose, if there is interest in that sort of solution (as hinted at the end of the original submission).

[Freeciv-Dev] [patch #3721] Getting rid of move_type dependency on unitselect dialog

Follow-up Comment #4, patch #3721 (project freeciv): Not being thread safe isn't just about whether the client is multithreaded. The entire computational system (client+server) has at least two threads, and if I read unit_move() correctly, send_unit_info_to_onlookers() is called a few times

[Freeciv-Dev] [patch #3721] Getting rid of move_type dependency on unitselect dialog

Follow-up Comment #5, patch #3721 (project freeciv): Oh, you were talking about server/client sync. Yes, even though client is single-threaded, and in that sense does a lot of things atomically, user action can happen between any two packets from server. As for transport and cargo being in

[Freeciv-Dev] [patch #3721] Getting rid of move_type dependency on unitselect dialog

Follow-up Comment #3, patch #3721 (project freeciv): While making things thread-safe in case threads are used in the future does have it merits, I don't see value in partial solution that just has smaller window for particular error, but is still not at all thread-safe. That doesn't make it one

[Freeciv-Dev] [patch #3721] Getting rid of move_type dependency on unitselect dialog

Follow-up Comment #2, patch #3721 (project freeciv): I don't think it is safe to use !can_exist_at_tile() as the filter if we're looking to exclude transported units: that implies an assertion that at any time the client is sufficiently idle to take a new command, no untransported unit cannot

[Freeciv-Dev] [patch #3721] Getting rid of move_type dependency on unitselect dialog

Update of patch #3721 (project freeciv): Assigned to:None = jtn ___ Follow-up Comment #1: Giving to jtn for him to decide if this fits to his select dialog plans.

[Freeciv-Dev] [patch #3721] Getting rid of move_type dependency on unitselect dialog

URL: http://gna.org/patch/?3721 Summary: Getting rid of move_type dependency on unitselect dialog Project: Freeciv Submitted by: cazfi Submitted on: Tue 19 Feb 2013 09:27:44 AM EET Category: client