Insert Slice surprisely unintuitive

I found spreading indexing in InsertSlice nodes surprisely unintuitive.
Probably because I didn’t use it often.
I post it here for a case, anyone would interpret it as a bug.

InsertSlice.v4p (8.0 KB)

I think the node was built to support declarative thinking, not imperative.
So basically all the indices refer to the original spread and not to the spread that already got modified by inserting the first slice.
On the left side you insert something before the 0th slice and the 1st, on the right side you insert two slices before the 0th slice. So for me, the result looks correct.

1 Like

For me too! I made a thread to show it’s not a bug.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.