thank you for your answer, I’m trying some new way that seems work… as soon as i found the way a will post it…
could be a bug inside the contour node…?
i am not quite sure what you’re up to, but there is an obvious flaw in your patch that may cause your problem:
below the Contour node you have the three SetSlice nodes. they all have an input spread of count 10. also their Slice Index pin can have a maximum of 10 slices, but the individual indices may overlap!
on an input spread of 10 slices a SliceIndex of 23 would set the same slice as a SliceIndex of 3 would. See the problem?
if you do it like this (make a buffer with setslice) and write to that buffer with the id you first need to sort the id indices (because contour ids jumps in their poristion in the spread ccording to their y pos). check the patch to see how…
yeah joregs is right. i just checked for indetical spreadcounts…
the ways you use setslice and select makes no sense…
but by the way its a nice trick to use that select setslice with contour with contour to create a buffer with a fixed spreadcount… i used that for my han style photobrowser, this way you get also automatically a touch down event for each touch…
@joreg I see the problem right now… off course :-) it wasn’t so hard to see… may be I was patching to many hours with out disconnect my head…
I was doing this kind of thing because I’d like to animate the coordinates that come out from the contour… and this normally generate confusion…
@elektromeier I check your patch but may be there is something that I don’t really understand because it seems me working not very good… may be I don’t understand very well how I can do…
the contourbuffer seems me do that I need and it was very helpfully.
I try modify it, and making one animated and seems me working…