Core concepts
A few terms recur throughout the Gantt Chart API. Understanding them up front makes the rest of the guides easier to follow.
- Chart vs. project.
TTMSFNCGanttChartrenders and handles interaction;TTMSFNCGanttProjectholds the tasks, states, and work-time calendar. Access the active project throughTTMSFNCGanttChart.Project. You can assign a separate project instance to share one schedule between views. - Tasks and the WBS. Each
TTMSFNCGanttTaskhas aName,Description,PlannedStart,PlannedDuration,Progress(0–100), andCost. Nesting tasks builds a work-breakdown structure; each task exposes a computedWBSstring and aSubTaskscollection. A summary task derives its dates from its children. - Durations and work-time policy. A duration carries a
Valueand aDurationType(gdtSeconds,gdtHours,gdtWorkDays). When a task usesgdtWorkDays, itsWorkTimePolicydecides whether non-working days and hours are skipped (whWorkTimeAndDays), only non-working hours are skipped (whWorkTimeOnly), or time runs continuously (whAllTime). - Dependencies. A
TTMSFNCGanttTaskDependencylinks two tasks with a type (gtdFinishToStart,gtdStartToStart,gtdFinishToFinish,gtdStartToFinish) and an optional delay. Dependency arrows are drawn automatically on the timeline. - States. A
TTMSFNCGanttTaskStateis a named, colored status with a priority level. States are reusable across tasks and can color the timeline bars. - Two panels. The control is split into a task list (configurable columns) on the left and a timeline (two-tier time header plus bars) on the right, separated by a draggable splitter.
See also
- Building a project — create tasks, subtasks, and dependencies.
TTMSFNCGanttProjectAPI