Improved Handling of Milestones
Release 2.4.1.3 introduced improved handling for the Importing and display of milestone data
Previous version of TC required that a task had both start date and start position as well as end position finish date in order to be drawn on the chart. Tasks that did not have these 4 values were not displayed.
The new version will always try to display a task providing it has at least one date and one position value. This makes it much easier to support milestones, which often only have one date value.
Example
In the previous version, a task withe values {startDate: 01/01/25 and startPostition:10} would not be drawn at all unless you also provided {finishDate: 01/01/25 and endPostition:10}.
In addition, you would need to provide a start shape (and or end shape) for the task to display (since you can't see a pixel of zero width).
In the new version, TC will draw each task as long as there is at least one position value and one date value, and it will do this regardless of whether the shape code library has a start shape or end shape.
- If a start date and start position are provided it will try to use the existing Shape Codes Start Shape settings (shape, colour and size).
- If the existing Shape Code Start Shape is set to none, TC will use a diamond shape, but still pick up the active colours and size.
- If a finish date and end position are provided it will try to use the Existing Shape Codes End Shape settings (shape, colour and size).
- If the existing Shape Code End Shape is set to none, TC will use a diamond shape, but still pick up the active colours and size.
In the event that only a start date and end position or finish date and start position are provided, TC will display a default shape, which is a black diamond of size 12.
These changes allow milestones to be displayed without the need to duplicate start and end date values and modify Shape Code Start and End shapes.
It also allows most shape codes to not require setting a Start Shape or End Shape to view milestones generated.