Ali Rostami

@Marti2203 @azinazadi Sorry for late reply. @Marti2203 I accepted a new merge request for the support of Java > 8.0. So please update the last commit in your code before...

Dear Mostafa, what would be the different between this time constraint by the weight of an Edge. These weights could be set also by GUI. Regards, Ali

Dear @mostafashaeritj, I do not know about dynamic networks. If you think it is needed definitely, we can add it easily. Regards, Ali

I changed the default value to "1", because I changed the default colour for vertex overall, but this problem is still there. A possible solution is to define two colours...

Again, this report is removed and is added as a new extension/algorithm. I did not check the functionality. The changes is going to be committed.

I do not get this bug, can you provide more details? A way to reproduce it?

I found a way to correct the problem but I did not push the new changes because i wanted to ask a question first: --- Is it really bad if...

I think it is however better than the current version because at least the user can see all the reports, although it is not the best implementation.

I tested different ones. It seems the problem comes only when k is equal to 2 or 3. It happens because the vertices in the second level are going to...

I corrected the positions. Please check if it is OK, close this ticket.