I noticed something odd: If I evaluate the Area of an unplaced room in Dynamo it returns a very strange value that appears to be neither null nor 0, see image. The list does contain doubles, not strings, I checked.
I do not know if the cause lies in the Object.IsNull node or the Element.GetParameterValueByName node. I did find 2 solutions:
1: Lunchboxes Room Element Collector evaluates the Area parameter via a Python script, see image in bottom right corner.
2: A Code Block workaround I cooked up throws an error, but seems to remain stable and does return a null value that I can then use in a mask.
So, what is the best solution?
First, given Ian Keough’s presentation at Case http://www.case-inc.com/blog/dynamo-now-dynamo-next I am leaning towards an approach that facilitates the collapsing of a Dynamo Graph into a Code Block. Would a Pyhton node be an obstacle in that process?
Second, the beautifull thing about Dynamo is that it circumvents the necessity of code syntax, be it C#, Python or Designscript. I’d rather stick with Dynamo nodes and simple Code Blocks. [Derailed train of thought] @Ian Keough: Will I be able to ‘explode’ a collapsed-into-designscript Code Block back into a Dynamo graph to allow a non-scripting user to adapt functionality? [/Derailed train of thought]
Third, my Code Block does throw an error. How seriously should I be taking that? Will this workflow be unstable?