Strange widget/gadget bugs

1. Units ordered to chicken out/retreat no longer stays in the retreat area. Their retreat is overridden by manual commands. I think this is bad because I prefer that they go interrupted to the repair area. I guess it come down to personal preference but I think I would prefer if units would ignore other orders unless you removed the Chicken out level.

2. Units don't lose their "settarget" when ordered to stop, at least for me. The "Keep target", cmd_keep_target.lua, widget is on by default.
This means that units might keep shooting at a target even if the player has ordered the unit to stop.
Is there a command that both cancels settarget and the orders?

@[RD]Godde
1.
There is a new option in Game->UnitAI->Retreat called "Auto deselect retreating unit"

With this option,
when you select a bulk of unit (such as Ctrl+Z) it will automatically remove retreating unit from your selection. But when you select only retreating unit (such as when all available unit is dead) it don't remove retreating unit from you selection and you can still move the unit around.

This is new options and might be buggy or annoying, but try it out.

Maybe make widget which automatically remove retreat zone which is occupied by enemy or out of LOS? (just a suggestion, I can't do that)

2. Situations where the "Keep target" is annoying.
a.You have a unit on hold fire. You order an attack on an enemy. Now your unit will keep firing at that enemy even if you tell it to stop.
b.You target an enemy factory while raiding but the enemy comes with their raiders and you would rather want your units to target the enemy units. But that requires you to cancel the settarget command or give an explicit attack order on an enemy. It is a bit unintuitive.
c.Also when the unit is using fight it keeps the settarget. So you might attack an enemy then order your units fight and the will keep firing at the the unit you first selected even though the fight command would have your units target something else. This behavior is fine but it is unintuitive that settarget have to be cancelled by an explicit settarget cancel instead of just a "stop" command.

I don't use the "Keep Target" widget, I just bound the commands to hotkeys. The widget exists partially as an example and mostly because I don't want to hide the entire settarget behaviour behind the UI. It implements reasonable default behaviour.

I can definitely confirm that the target is kept, especially for ground units.