Code method question

(Claudiu Cristea) #1


I noticed that the SchedulerImpl::schedule method is triggered for all the tasks of a project when we perform operations such as: copy + paste, delete, add, draw dependency. This seems highly inefficient when the project grows to a considerable number of tasks.

What was the reason behind choosing to check all the tasks, instead of just checking the ones involved in the operation?

Thank you !

(Dmitry Barashev) #2

Running the algorithm over the whole graph is easier to implement and is more robust. Talking about efficiency, if you’re aware of any real project where exactly this method becomes an issue, please let us know.

(Claudiu Cristea) #3

Thank you for the answer ! I added many tasks and resources and the program started lagging a bit when I drew dependencies between several tasks.