Tactical Element class and behavior

[orbitusii]

Tactical Elements are static, non-track objects present on the scope that can provide a variety of useful information. TEs may represent:

• Airfields
• SAM Sites (with range rings)
• Defended/Target Points
• Bullseye Points

Data each of them will require:

• World-space coordinates (i.e. Vector64 type)
  • Getters/Setters to get this as LatLonCoords
• Type (i.e. SAM, Airfield, etc.)
• FriendFoeStatus
• Symbology getter => should reference Program-level symbols and brushes
• Optional Range Ring(s) that will be drawn on the map

TEs should be imported from KML Point-type placemarks or added by hand on the scope

• If a TE comes from a KML, it should be marked as such and not serialized
• If a TE is added by hand, it should not be marked like a KML TE and serialized

TEs should have some sort of reference table for commonly-used types (like specific types of SAMs) that can be used to autocomplete certain values, like Symbology and Range Ring(s) (this may be a separate issue at some point)

[orbitusii]

TEs implemented, rendering, and happy-ish for now. Can be imported from Data Sources after the Data Source has been activated.

Need special graphics for rendering but they function!

[orbitusii]

Serialization thoughts

• TEs should have a boolean called "Serialize" or something that controls whether a TE is serialized
  • TEs created via the right-click menu should Serialize by default
  • TEs imported from KMLs should not be Serialized by default
  • TEs imported from Data Sources should not be Serialized by default
  • TEs selected for Bullseye references should be serialized regardless of their "Serialize" settings and reimported on application load
• The file TEs are saved to should default to AppData, but with options to export to other locations for sharing