I have a strange bug from List.Combine that I cannot replicate for simpler definition.
but here is an image where i show that substituting List.Combine by a small script does the job while List.Combine fails giving a null value without apparent reason:
Yeah, it’s akways better to use python. Sometimes ppl ask on the forum how to do sth and they tell you use built-in nodes Your example is just perfect. Nothing is so simply, especially when you are working on bigger data sets and floats. It’s like casting integer to string and getting decimals
Just curious, could you try adding ‘object to string’ before combine? Or round up these values?
Not really, specifically when you start to look into how stuff scales and is maintained. One graph, you’ll never want to reuse, and which can live on forever, sure. But imagine having to update every python node in every graph you’ve ever written due to a breaking syntax change. Had you used an OOTB node you’d already be done, as Dynamo would handle such a change automatically. Had you used a custom node, you’d have to make the change once, save the node, and all the graphs would be updated.