For global leader lines, we need to be aware of when they are set since (AFAICT) if a global leader line direction is set for an aircraft, it overrides a controller's local per-aircraft leader line direction and similarly, if a controller sets a per-ac leader line direction, it overrides a global leader line direction.
Therefore:
Setting the global leader line direction for an aircraft now posts an event to EventStream; STARSPane pays attention to this.
STARSAircraftState now stores a bool UseGlobalLeaderLine to indicate whether to use the local or global one if both are set.
Other fixes:
[Multifunc]L5* clears the 'controlled by other controllers' leader line direction setting (4-98)
Leader line commands now use calculateController to look up TCPs (and not World GetController!)
Cleaned up the code that distinguishes between setting a per-aircraft leader line direction specified using ACID ([Multifunc]L(#) (ACID)) and a per-controller leader line specified via TCP ([Multifunc]L(TCP)(#)).
For global leader lines, we need to be aware of when they are set since (AFAICT) if a global leader line direction is set for an aircraft, it overrides a controller's local per-aircraft leader line direction and similarly, if a controller sets a per-ac leader line direction, it overrides a global leader line direction.
Therefore:
Other fixes: