Bug #1566: Do not launch exception in MonteCarlo view is critical path is only a milestone

In the MonteCarlo perspective the critical paths were appear empty and the
button to calculate it will be disabled.

FEA: ItEr77S04BugFixing
This commit is contained in:
Manuel Rego Casasnovas 2012-11-20 17:24:08 +01:00
parent d76e3d36d7
commit 6e24103b73
2 changed files with 5 additions and 1 deletions

View file

@ -301,7 +301,8 @@ public class MonteCarloController extends GenericForwardComposer {
feedCriticalPathsList(); feedCriticalPathsList();
reloadGridCritialPathTasks(); reloadGridCritialPathTasks();
} }
btnRunMonteCarlo.setDisabled(criticalPath.isEmpty()); btnRunMonteCarlo.setDisabled(monteCarloModel.getCriticalPathNames()
.isEmpty());
} }
private static class CriticalPathTasksRender implements RowRenderer { private static class CriticalPathTasksRender implements RowRenderer {

View file

@ -84,6 +84,9 @@ public class MonteCarloModel implements IMonteCarloModel {
return; return;
} }
this.tasksInCriticalPath = onlyTasks(tasksInCriticalPath); this.tasksInCriticalPath = onlyTasks(tasksInCriticalPath);
if (this.tasksInCriticalPath.isEmpty()) {
return;
}
Collections.sort(this.tasksInCriticalPath, Task.getByStartDateComparator()); Collections.sort(this.tasksInCriticalPath, Task.getByStartDateComparator());
initializeTasksInOrder(getOrderFor(this.tasksInCriticalPath)); initializeTasksInOrder(getOrderFor(this.tasksInCriticalPath));
initializeOrderNameFor(this.tasksInCriticalPath); initializeOrderNameFor(this.tasksInCriticalPath);