3. Schedule tasks

Automatic and manual correcting of dependencies by moving related tasks

• See documentation for Correcting dependencies and Algorithm for correcting dependencies.
• The correct dependencies are shown blue, the incorrect dependencies in red. The colors can be changed, see tutorial 02-Dependencies
• Attribute

  GanttIncorrectDependencies

  controls which dependencies will be marked as incorrect.
  For 1 will be marked as incorrect only dependencies that start (+lag) before they end.
  For 2 will be marked as incorrect all dependencies that don't start (+lag) and end on the same date.
  For individual dependency it can be changed by float value in the dependency definition (after the !).
  
• The dependencies are corrected by moving the related tasks. The tasks are never resized in this action. The tasks are never moved to violate their constraints.
  When moving task that consists from more parts, all the parts are moved together, preserving space (in worktime) between parts.
  Only Gantt objects defined in GanttTask can have dependencies.
• The dependencies can be corrected manually by clicking to the first button (Correct) on toolbar.
  Or by choosing item "Correct all dependencies" or "Correct related dependencies" in the Gantt popup menu.
  Or by calling the action CorrectAllDependencies or CorrectDependencies by API or assigned to some event.
• The dependencies can be corrected automatically (or by user confirmation) after any change in the chart (task move, resize, delete, create, constraint change or dependency change), according to

  GanttCorrectDependencies

  attribute value.
  The one changed task can be also automatically corrected or it can be fixed and all other tasks are moved to correct the dependencies, it is controlled by GanttCorrectDependenciesFixed attribute. It affects task or dependency change, but not constraints change.
• There are

  three methods of correcting dependencies

  , chosen by

  GanttStrict

  attribute.
  By default (for 1) are all tasks moved as close to project start / end date as possible.
  For 0 are the tasks moved as little as possible to only correct the dependencies.
  For 2 are all descendant tasks moved as close as possible to their ancestors. See documentation for Algorithm for correcting dependencies.
• A user can move the task manually and preserve this position when moving the task for correcting dependencies. The task is never moved before this manual date.
  It is controlled by GanttManualX and GanttManualChange for main bar and GanttRunManual and GanttRunManualChange for run bar.
• It is possible to schedule the tasks from project start or project finish, it is set by

  GanttDirection

  .
  

• Circular dependencies

  checking is controlled by

  GanttCheckDependencies

  , it is possible to restrict, permit or ask the creating.
  The tasks containing circular dependencies are usually impossible to correct.
  
• By attribute

  GanttFixComplete

  is possible to fix all already started tasks (with Complete>0) and move only not yet started tasks (Complete=0).
  In this case dependency between two already started tasks is always marked correct.
• Disabled and locked task is never moved when scheduling.
  Disabled task has also disabled dependencies, they are not used when correcting dependencies.
  
• If scheduling Run box, it is possible to move the box freely or preserve the box order or to not overlay the boxes by GanttRunCorrectBox.
  
• In large charts when some dependencies still remain incorrect after correcting dependencies increase value of GanttMaxCorrectingLoops.
  Increasing it can slow down correcting especially if the dependencies cannot be corrected due constraints or circular dependencies.