Setting aside the fact that these are a bit over-determined (because
setting patch size may conflict with the window dimensions), I believe
the settings are not honored at start up.
Well, I'm hesitant to refer to the "widget format" document as a "widget
specification" (as title of this thread suggests), since it wasn't
really written for that purpose. The intention was *not* to provide a
way for people to customize a model's interface from outside of NetLogo,
or to get NetLogo to do things that you can't make it do through the
widget editor. To a limited extent, the document can be used for that,
yes, but that's not its intended purpose.
Instead, that document was made as a canonical record that explained
(e.g. for someone who might want to write a widget parser for a
browser-based version of NetLogo) how many slots each type of widget
had, what type of data to expect in each of those slots, and what the
NetLogo codebase claimed the purpose of that slot was. Basically, the
document was made so that programs know how to interpret what NetLogo is
writing out. Ideally, the document /would/ be a specification that
NetLogo conformed to. But that would require some serious tuning-up of
various NetLogo widget behaviors, and a cleanup of the digital detritus
that the NetLogo file format has accumulated over the years. While
desirable, I don't see that happening in the near future.
- in some models the control widgets in the View are irrelevant,
but they are controlling available display possibilities
Actually, there seems to be a consensus amongst us that those "resizing
arrows" are irrelevant in nearly *all* cases. I feel like I could
produce a lengthy list of problems with the continued presence of the
those buttons, but I fear that I would just be brutalizing thin air,
since no one is likely to rush to the aid of those poor, little arrows
of a time long past. Consequently, we have opened a ticket
<https://github.com/NetLogo/NetLogo/issues/930> in our issue tracker for
reducing the amount of cruft attached to the View widget, and we intend
for those arrows (and probably the "3D" button) to be removed in a
future version of NetLogo.
On 02/07/2016 10:11 AM, Alan Isaac wrote:
The View documentation at
https://github.com/NetLogo/NetLogo/wiki/Widget-Format still suggests
that it is possible to set the view parameters. Setting aside the fact
that these are a bit over-determined (because setting patch size may
conflict with the window dimensions), I believe the settings are not
honored at start up. Specifically, if the specified width of the
window is very thin, I deduce that it is overridden to the minimum
necessary to display the control widgets (and by default, the tick
counter). A particular loss is the response to setting a patch size of
-1, which used to hide the view. (It seems one can still
`set-patch-size` to a larger negative number to effectively hide the
view, but not in the widget specification.)
This seems to raise multiple issues:
- I recall developer agreement that it should be possible to hide the
view,
which is irrelevant to some models,
but this has become messier rather than easier
- in some models the control widgets in the View are irrelevant,
but they are controlling available display possibilities
Apologies for the multiple recent posts: issues tend to arise at the
semester start. (I'll stop posting now, unless I find something serious.)
--
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]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
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.
