That seems too implicit to me. Being able to set default values would be useful for other reasons besides allowing more deterministic model startup. Currently the model will startup with e.g. sliders at the values the user last set before saving the model. This interacts with BehaviorSpace experiments: one must specify every slider, chooser, and switch value, or risk that a user will accidentally run an experiment with unintended values. This is a burden when there are many experiments and many widgets. I believe would be more natural to have default values on these widgets, which would be used when no values are explicitly set in BehaviorSpace. IIUC, this has become even more important since version 5, since startup no longer runs headless or in background BehaviorSpace runs. I think this means that the old work around of setting "default" values of widgets in startup won't work if one is running experiments headless.
-- You received this message because you are subscribed to the Google Groups "netlogo-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
