I'd like to add to it that the problem is caused by a carrier who wants to deliver something and he can't cause it's full and when exactly THAT carrier is the only possible solution to solve the deadlock. He's standing there with a log in his hands while everyone is waiting for him to remove stuff from that point.
I'm also a programmer and would take a look at it if I didn't have my thesis at my head but I think it can be solved in one line of code by allowing a 'carry-guy' to put down his resource while going over the 'limit' if he makest the promise he takes something with him. Later on it would also be nice to implement a way to see that a flag is getting too much resources stocked by just changing the color of the flag or putting an exclamation mark on it.
Hi,
I just was going to report the same bug: 192.168. 1.200/~ bderooms/ deadlock. png
http://
I'd like to add to it that the problem is caused by a carrier who wants to deliver something and he can't cause it's full and when exactly THAT carrier is the only possible solution to solve the deadlock. He's standing there with a log in his hands while everyone is waiting for him to remove stuff from that point.
I'm also a programmer and would take a look at it if I didn't have my thesis at my head but I think it can be solved in one line of code by allowing a 'carry-guy' to put down his resource while going over the 'limit' if he makest the promise he takes something with him. Later on it would also be nice to implement a way to see that a flag is getting too much resources stocked by just changing the color of the flag or putting an exclamation mark on it.
I hope that helps,
Brecht