Change History WSMS 3.0.4.Rev 4 (WSMS3044)

Added Features
(SCR1099) CSC Support for Mil2525 MOOTW symbols
(SCR1100) Add ability to redefine Mil2525 point ordering for strict compliance to the standard
(SCR1101) Add Mil2525 style options to allow user defined annotation color
(SCR1102) Add Mil2525 style options to specify font or stroke font for tactical annotation
(SCR1103) Add Mil2525 style options to size the stroke font characters
(SCR1104) Add Mil2525 definition option to force a winding order
(SCR1105) Added new component wsms-terrain-position to provide operations to snap a position to terrain features
Bug Fixes
(SCR1081) Corrected road following planner where it would deviate from roads
(SCR1106) Corrected color used for Mil2525 Suspect symbols
(SCR1107) Corrected arc direction in Mil2525 Task-Delay and Task-Relief
(SCR1108) Corrected rendering of Mil2525 Task-Disrupt and Effects-Disrupt
(SCR1109) Corrected direction of Mil2525 base supports for Attack-by-Fire and Support-by-Fire
Special Notes
(SCR1100) Added Mil2525 definition (mil2525b.vti file) option called "Ordering" that allows the WSMS point order to be modified. E.g.
           -- Air Corridor
           Identifier  G*G*ALC---*****
           Points      Triple
           Filename    $ROOT/tactical/221221.CGM
           Text        Middle_Top "CORRIDOR %IDENT"
           Text        Middle_Bottom "%COMMON"
           Ordering    2 3 1
This indicates that WSMS Points A, B, C on a call to Get_Locations_Strict() will return the points in the order B, C, A. Similarly a call to Set_Locations_Strict() will apply the points given in say the order B, C, A and will maintain them internally as WSMS ordering A, B, C. This is used to enable external Mil2525 applications to better map their source points to the WSMS and representation and for WSMS to export its Mil2525 locations to comply with external Mil2525 applications.

(SCR1101) Added Mil2525 style option Style.Foreground for a user defined foreground color to be applied to a symbol. Used in conjunction with Style.Font_Override set true the annotation color used for the symbol will be the Style.Foreground instead of the standard affiliation color.

(SCR1102) Added Mil2525 style option Style.Stroke which when set true indicates the internal stroke font is to be used for tactical annotations (this was the method used in previous WSMS releases). When set false indicates that's the Style.Font is to be used for tactical annotations, this is generally a more readable font but looses the ability to rotate with the symbol.

(SCR1103) Added Mil2525 style options Style.Stroke_Width to specify the pixel width of the stroke font lines. Style.Stroke_Size is used to specify a pixel width and height for stroke font characters.

(SCR1104) Added Mil2525 definition (mil2525b.vti) option called "Winding" which allows a winding order to be forced for multipoint symbols. E.g.
           -- Strong Point
           Identifier  G*M*SP----*****
           Points      MultiClosed
           Filename    $ROOT/tactical/2214131.CGM
           Text        Middle_Top "%IDENT"
           Text        Middle "%SIZE"
           Winding     Clockwise
The values are Clockwise, Anti_Clockwise and None. None is the default when the value is not applied to a symbol. When a winding order is specified for a symbol all the entered points are checked before rendering and reversed if they are not in the specified winding order. Concave shapes will force the winding order to remain unmodified. This is useful for symbols that have a specific inside/outside shape. By specifying the winding order the inside/outside direction of the shape is forced to be in one direction.

(SCR1105) Added component wsms-terrain-position that provides operations to help snap positions (normally GPS) that might not exactly be on a terrain feature such as a road. The operation smooth is intended to provide a simply means to smooth something like a GPS position that has a tendency to jump by maintaining the position within a specified radius…. most useful for small changes in position. Snap() provides the ability to snap the specified position to the closest vector feature currently set in the terrain instance. This if your terrain instance contains a vector road layer then calling snap with a position within the specified radius of a road vector will return the closest position exactly on the road vector.