Opened 9 years ago

Closed 8 years ago

#3302 closed defect (duplicate)

[PATCH] missing control for deactivating guard order in mixed selection

Reported by: Kalle Richter Owned by: svott
Priority: Must Have Milestone:
Component: UI & Simulation Keywords: patch
Cc: Patch:

Description

After ordering a selection x of units to guard a unit y it's not possible to undo this order if a selection x' (with x being a subset of x') is selected. Units refuse orders and return to guard the unit and commit suicide.

experienced with d884ffa0b1c763742dae483a474c327d06ff4d7a

Attachments (1)

3302.js.patch (3.9 KB ) - added by svott 8 years ago.

Download all attachments as: .zip

Change History (12)

comment:1 by Stan, 9 years ago

Could you attach a system_info.txt, and a minimal testcase ? (Small map with few objects)

by svott, 8 years ago

Attachment: 3302.js.patch added

comment:2 by svott, 8 years ago

Keywords: simple patch added
Owner: set to svott
Summary: missing control for deactivating guard order in mixed selection[PATCH] missing control for deactivating guard order in mixed selection

I just add this.RemoveGuard() to the orders. The number of adds doesn't look nice, but tell me if there is a better solution I am also not sure if I missed something or added to many remove-calls.

comment:3 by Imarok, 8 years ago

(If you want your patch reviewed you have to add the "review" keyword)

comment:4 by elexis, 8 years ago

Component: Core engineUI & Simulation
Keywords: review added
Milestone: BacklogAlpha 21

comment:5 by fatherbushido, 8 years ago

(It seems you forget to remove the warning L4914.)

comment:6 by svott, 8 years ago

I think I mentioned that in IRC and it is not enough to spend time for uploading another version

comment:7 by sanderd17, 8 years ago

I think it should be possible with altering fewer lines. Did you try adding a RemoveGuard call to the "leave" functions of the INDIVIDUAL.GUARD state?

comment:8 by svott, 8 years ago

I tried and it does not work that way because a guarding unit always leaves the guard state when the unit stops - but the guarded attribute is still set

comment:9 by fatherbushido, 8 years ago

I don't understand the issue of the ticket, is it yet fixed ? Guard order should be explicitly cancel, when doing that i have not the issue.

Version 0, edited 8 years ago by fatherbushido (next)

comment:10 by fatherbushido, 8 years ago

Keywords: review removed

comment:11 by elexis, 8 years ago

Keywords: simple removed
Milestone: Alpha 21
Resolution: duplicate
Status: newclosed

Indeed not a simulation but GUI issue. Closing a duplicate of #3823.

Note: See TracTickets for help on using tickets.