Different inputs for an "IF" node issue

[PauLtus]

I came across a pretty interesting problem:

@Zschlave posted a question about lists with subitems:

List which have subitems and sometimes not

Not sure how to explain my question which have bothered me for some hours now, but ill try anyway. The problem im having is that my dynamo script sometimes has a list with sub items, and sometimes not. When im using list.map i can only get it to work on either cases, but not both. I bet there is an easy solution for this, but i cant seem to find it. See picture for both cases. Case 1 (With sublist) [image] Case 2 (No sublist) Could not add another image because im a new user. Link: https:…

I thought I had found a solution:

List which have subitems and sometimes not

I’ve made something that I think should work but it doesn’t… I am working in version 0.9 however so it might work in a newer version. [image] Or maybe I’m an idiot and this simply shouldn’t work, I’d like to hear either way.

As you can see it doesn’t work.

@kennyb6 responded to me and we figured there needs to be a degree of consistency between the true and false inputs.

List which have subitems and sometimes not

[if2] Same thing if its a single element. When you make it a list before putting it into the true input, the single element false input is made into a list as well.

Anyway. I thought I’d just share the issue here. I’m not necessarily looking for a solution (although you might indirecly solve @Zschlave’s problem with it). I do already know that creating the same thing with just a code block doesn’t work either (in fact that was the first thing I tried).

[viktor_kuzev]

I see 2 approaches here:

[PauLtus]

I’m not completely sure what happens here (my Python knowledge really isn’t good enough for that).
If I’m understanding correctly, with the first python script you’re basically doing what I was doing in Dynamo but in Python, which then works because it’s in Python.

[viktor_kuzev]

Here’s a node approach for the second option:

[kennyb6]

As @Ritesh_Chandawar pointed out in the other thread, there is another node that works the way @PauLtus wants, which is ScopeIf. It does not matter what the structure of the true and false inputs are, it will return it as is.

[PauLtus]

I saw it.
Pretty funny these things just happen to exist.
I do wonder why you’d ever use the regular If node then. Might be more efficient, maybe you occasionally want the error to show up before there’s a bigger problem spreading though the entire code.

[kennyb6]

I guess in a way, if node is like if + normalize depth built into one, which may be more useful or rather more common than a non normalized depth testing.