* Added listbox with list of progress types; now it should refresh the progress of each
task whenever a new type of progress is selected
FEA: ItEr64OTS04ReporteAvancesCadeaCritica
The problem lied in that when moving the origin of the end - end
dependency backwards so the new start was violating the incoming
end-start dependencies. Now the start is checked after.
FEA: ItEr63OTS03PlanificacionHaciaAtras
Otherwise the destination task of a end-end dependency would not move
if the origin task is moved to a prior date.
FEA: ItEr63OTS03PlanificacionHaciaAtras
In the task that initializes the recalculations the end must be
calculated always. Otherwise it could ignore the effect of the
incoming end dependencies if the start is not modified due to
dependencies.
FEA: ItEr63OTS03PlanificacionHaciaAtras
visible END-END dependencies to a container and visible START-START
dependencies from a container are forbidden to simplify the critical
path calculation.
FEA: ItEr63S03BugFixing
The end date for task groups was not always being calculated. Now when
it is a parent recalculation the end is always calculated, this
ensures that the container has initially the right size since the
parent recalculation is always done.
FEA: ItEr63S03BugFixing
* Added configuration option for enabling this menu tab
* Montecarlo method calculates a range of enddates and its corresponding
likelihood. For each task of an order, there are three possible
durations (pessimistic, normal and optimistic). Each duration is
associated with a likelihood value. A montecarlo calculation, generates
for each task a random value and takes the duration of the task
associated to this random value, summing each value for each task, the
resuling value is the hypothetical enddate of that order. This operation
is executed n times. The higher the value, the more accurate the
results, although there is a threshold limit.
FEA: ItEr63OTS06MonteCarlo
Now the mode is changed after hiding the previous tab, so the previous
tab is not repainted and the new tab is showed with the correct mode.
FEA: ItEr63S03BugFixing
The problem lied in that the end date of the task group was being
updated keeping the length when the start changed. Since the children
of the group were not modified when adding the milestone the end date
was not recalculated and the wrong value persisted.
Calculating the end date keeping the length in task groups is
incorrect since their end date doesn't depend on the previous length,
but in the incoming dependencies. Several refactorings and
simplifications applied thanks to this insight.
FEA: ItEr62S05BugFixing
