The background position of the current day and deadline was outside the
visible area in the timetracker watermark columns when it was on the
last day of the interval.
A better alignment with the tasks layer (reducing the 3px max deviation)
on this cases can be achieved by revamping how lines and borders are
represented on the watermark layer.
FEA: ItEr76S04BugFixing
The background position of the current day and deadline was outside the
visible area in the timetracker watermark columns when it was on the
last day of the interval.
A better alignment with the tasks layer (reducing the 3px max deviation)
on this cases can be achieved by revamping how lines and borders are
represented on the watermark layer.
FEA: ItEr76S04BugFixing
doAfterCompose instead of constructor.
When doAfterCompose is run, we are sure we are ready to send messages to the
client side.
FEA: ItEr76S04BugFixing
doAfterCompose instead of constructor.
When doAfterCompose is run, we are sure we are ready to send messages to the
client side.
FEA: ItEr76S04BugFixing
When a task is potentially modified is not needed to change the start
and the end date. This was causing two invokations of the
"dependencies" algorithm. Now only one is done.
Although the constraint is not applied it must be provided. Otherwise
the dominating forces would not take it into account. Normally this
wasn't a problem since if the secondary point date changes it was
provided. But it can happen that the secondary point doesn't change,
in that case the constraint must still be taken into account.
When a task is potentially modified is not needed to change the start
and the end date. This was causing two invokations of the
"dependencies" algorithm. Now only one is done.
Although the constraint is not applied it must be provided. Otherwise
the dominating forces would not take it into account. Normally this
wasn't a problem since if the secondary point date changes it was
provided. But it can happen that the secondary point doesn't change,
in that case the constraint must still be taken into account.
correct constraint based on the scheduling mode.
To do that, the scheduling mode, start and end date are needed as parameters.
FEA: ItEr76S04BugFixing
Conflicts:
libreplan-webapp/src/main/java/org/libreplan/web/planner/TaskElementAdapter.java
This change implements the behaviour described in the analysis that you can
easily understand with the following example:
1) Initial scenario:
* Task leaf "A" (0 hours)
* Task leaf "B" (20 hours)
2) Indent task leaf "B"
3) Final scenario:
* Task container "A" (20 hours)
|- Task leaf "B" (20 hours)
FEA: ItEr76S13WBSSettingUpBehavior
