Thank you Jonas for replying, as you can see from the image below , the console results of the rectangle is something of the first step I want to achieve as the intial state of the polygon have the same amount of edges as the final stage and that there are two arrays showing there initialand final edge lengths. But in real life the polygon we get are more like the polygon on the right and hence there is more stages in between to reach the final stage. Hence I would like to know how to store the arrays of the inbetween stages.While having the ability to reuse it t later stages or until it is overwriten.
Attached are the sample file thats similar to what I am currently using. Using set attribute operation to create a simple lookup table, but it is only good if the polygon doesnt have a many edges, and that at the later stages the extruded level are limited to single digits. Other wise it will be very messy and creates so much redundancies handful.
So if an array can be used in a function(rather than as a global declearation) while its result is global and be used any level child of the parent polygon like the Set operation for constants and floats,
as such:
arrayA= comp(fe) { all : scope.sx }
@StartRule
saveArray-->
cleanupGeometry(all, 0)
set( arrayB, arrayA)
godosomethingelse.
X.
i
The Second question
My understand of in order to use the setback per edge we must first edit the edge attribute function
and for a hand full of test samples working with the way as suggested by the page would be ok.
However when trying to use it on a large scale of dataset of say 50K -500k polygon set with an average of 4-8 edges per polygon, where do you think it will be sitting on this graph?
Hence my second question of; is there any code based way of altering the edge attribute array?