Why is the delete output 72 and not 8?
Is a filled region made up of 9 items?
1 Like
This is common behavior when deleting things.
For example, delete a view and see how much deleted sub elements you get then:
5 Likes
yes… but as I asked… WHY?
Is a filled region made up of 9 items?
Probably the boundary lines. Weird though! I dont believe if you use the API method it works that way so it might be built into the node that way to report sub elements as well.
1 Like
Certainly an unideal degree of reporting for verifying element deletion count vs totals.
@Alien maybe try my element.delete node in Crumple which has exposed Python also if you want to see an alternative that doesn’t return sub elements.
1 Like
Yes think so…ut how do your node handle it ? as if i look at genius loci it seems it do the same…if i use archilab it just give a bool …true or false…but think its actuelly do the same as well
I send out a true/false list that you can mask afterwards using filterbyboolmask to get the failing elements.
I have a try/except it goes through to catch the failures.
1 Like
Here is an interesting example that shows that deleting an element sometimes is the only method to get access to the sub elements.