For an extension recently, it came up in discussion that one of the ways that the extension could update itself would be by listening for NetLogo events for ticks, rather than requiring the model writer to repeatedly call the command. This might lead to the context being held by the extension to grow stale. However, for an extension that boots up a secondary view (and indeed, reworking hubnet to be something akin to such an extension), having things work in the background feels desirable.
Would it be better to root out all instances where the currently used context gets reset (if there are actually any) or provide extensions a mechanism by which they can get the recent extension as they wish? Or is this entire line of thinking wrong for some unknown reason? Assumedly if NetLogo were to ever become based on immutable states, it would break this pattern, but that's not very likely in the first place. Frank -- 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.
