Hi all,
“Earlier”, when I had one surface and multiple parameters, the “default” list level access was exactly what I wanted in the GetIsoline node:
):“Earlier” the selection node was Select From Alias.
Now the selection node is Select From Alias as List.
List.FirstItem should clear things up to remove the structure. Alternatively you can use the other node (assuming it still exists, if not we’d have to escalate to the Alias team).
Well caught! Haha, funny that I, who actually triggered this change, need to be reminded by you on it. However, even though not being a regression then, I don’t really like the auto handling of list level access from Dynamo here:
You have a list with one entitiy, and a list with n. Why would the automatic procedure prefer a 1 to 1 handling over a 1 to n handling?
I can assure you that I myself would nearly ALWAYS want the “1 to n” handling?
Auto lacing defaults to shortest, unless one of the inputs is a single item, in which case auto moves to longest lacing.
While you might say that now, you’re approaching things from a geometry perspective rather than an assembly perspective. Geometry wise it’s not an issue, but when you get into Revit models with 1000’s of relationships if the default was longest we’d get a LOT of bad results as we do stuff like pushing room numbers as a prefix to the range of values which are inside the room… or when placing 10,000 instances of six different types of 4 point adaptive components with 10 nested parametric families that make up a tower façade suddenly defaulting to longest lacing means you have panel types atop each other, or worse duplicated panel types which you can’t see.
Okay, fair point!
