We need to create some example models that have the forever button removed, replaced with an "on" switch.
We should do this just by refactoring a few models (Disease would be a good place to start). The go procedure should check if "on" is true, and if so, then run the rest of the code. However, since this is run in a tight loop, we need to have a check for hubnet-message-waiting outside this if statement, instead of inside it. The reason for this is that hubnet-message-waiting throttles the cpu usage (Thread.sleep(50), I think), so that the model doesn't chew up all the cpu when the "on" switch is turned off.
Sergey, please see if you can experiment with this and get a few models up and running and see how they do.
We need to create some example models that have the forever button removed, replaced with an "on" switch.
We should do this just by refactoring a few models (Disease would be a good place to start). The go procedure should check if "on" is true, and if so, then run the rest of the code. However, since this is run in a tight loop, we need to have a check for hubnet-message-waiting outside this if statement, instead of inside it. The reason for this is that hubnet-message-waiting throttles the cpu usage (Thread.sleep(50), I think), so that the model doesn't chew up all the cpu when the "on" switch is turned off.
Sergey, please see if you can experiment with this and get a few models up and running and see how they do.