From cce801ee1ca7b43d9edf5ac59b5bf1f76c8c50d5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jacobo=20Aragunde=20P=C3=A9rez?= <jaragunde@igalia.com>
Date: Thu, 1 Mar 2012 17:45:19 +0100
Subject: [PATCH] Remove redundant call to scheduling algorithm from
 TaskPropertiesController.

The algorithm is already being called from ResourceAllocationController.

FEA: ItEr76S04BugFixing
---
 .../web/planner/taskedition/TaskPropertiesController.java  | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/libreplan-webapp/src/main/java/org/libreplan/web/planner/taskedition/TaskPropertiesController.java b/libreplan-webapp/src/main/java/org/libreplan/web/planner/taskedition/TaskPropertiesController.java
index da83b74a8..232d86e6a 100644
--- a/libreplan-webapp/src/main/java/org/libreplan/web/planner/taskedition/TaskPropertiesController.java
+++ b/libreplan-webapp/src/main/java/org/libreplan/web/planner/taskedition/TaskPropertiesController.java
@@ -269,9 +269,10 @@ public class TaskPropertiesController extends GenericForwardComposer {
                         .getValue())) : null;
         if (taskConstraint.isValid(type, inputDate)) {
             taskConstraint.update(type, inputDate);
-            if (currentContext != null) {
-                currentContext.recalculatePosition(currentTaskElement);
-            }
+            //at this point we could call currentContext.recalculatePosition(currentTaskElement)
+            //to trigger the scheduling algorithm, but we don't do it because
+            //the ResourceAllocationController, which is attached to the other
+            //tab of the same window, will do it anyway.
             return true;
         } else {
             return false;