tag:support.nodebox.net,2012-11-01:/discussions/nodebox-2-3/52-output-type-of-a-subnetworkNodeBox: Discussion 2014-02-11T22:20:32Ztag:support.nodebox.net,2012-11-01:Comment/236557392013-01-15T10:28:04Z2013-01-15T10:28:54ZOutput type of a subnetwork<div><p>Hello, I figured out why this happened but the reason is quite
technical: turning the output range to value causes the output to
be basically organised in such a way (if you really want to know, a
"list of a list of geometry objects") that the code is trying it to
feed as an argument of a function that is not really capable of
handling it.</p>
<p>That said, it's not a good idea to set the output range of sub
networks to value. Yes your output inside the subnetwork might be
treated as a single object and from that perspective it makes sense
to make the network have output range value. But... the subnetwork
itself wraps whatever is inside of it into a list anyway, so from
the subnetwork's point of view it makes more sense to always have
output range list.</p>
<p>But we agree it's confusing and we'll think about how we can
approach this issue.<br>
<a href=
"https://github.com/nodebox/nodebox/issues/311">https://github.com/nodebox/nodebox/issues/311</a></p></div>Stefan Gabriels