heatbugs minor omissions?; suggestion

[glen e. p. ropella]

"rlr" == Rick Riolo <address@hidden> writes:

[...]
rlr> A suggestion for future versions of heatbugs:

rlr> Change it in some way so that at least some of the parameters can
rlr> have an effect when changed during a run, via the GUI, e.g., the
rlr> randomMoveProbability, the evaporationRate and the
rlr> diffuseConstant.

rlr> In the short term, maybe there could be a method tied to a button
rlr> that says "Apply Changes" which passes the changed values along
rlr> to the appropriate objects.

rlr> One longer term solution to that problem might be to make it
rlr> possible to assign a "update" method to variable probes, so that
rlr> if one is assigned, when <Return> is pressed to set a variable,
rlr> that method gets executed.  The user could then define it to do
rlr> error checking, or to pass values along to other objects.

rlr> Or maybe there are other better ways to achieve this.

Thanks for the suggestions, Rick.  Barry, JJ, and now you have 
suggested that heatbugs needs a revamp.  I planned on doing it.
What you seem to be implying is the same type of User Interface
object Barry uses in SCL.  It's not really a modelSwarm probe,
but more of a space/agent editor.  I don't think this is a bad
idea.  The model-wide changes could be handled this way, as well.

glen