variant App::Link

[paullee]

Well, those exposed Link array elements are ordinary Links in many sense, except that it can't be used to make further arrays. When you delete the parent Link, those elements will remain, and you can use them like normal Links. So I don't think it'll help with your use case.

If I undstandard correctly, your use case is better to be abstracted as some type of attachment method, so that it can be reused to work on any object with the AttachExtension.

Continue discussion about Using Method in Linked Object

Have another idea, hope it make sense, to easier manage each instances in fact on about my idea on attachment as well as on @Zolko's on varied shape.. just a concept.

Link produce an Array, then say a series of parameters is input in the 'Parent Link' to assign to each of these array Elements rather than inputting at every Elements (/child instances):-

1. Say in the Link / LinkWindow, has a Property of Offset-X(s)...
2. A series of Offset-X pattern user input like, [1, 2, 1, 4, 1, 2....]
   (or generate by a formula / Node Editor @microelly2 is working on?)
3. So the Link / LinkWindow 'automatically' assign to its ArrayElements...

   Code: Select all

   for n, i in enumerate(Array):
       i.Offset-X = obj.Offset-XS[n]
   

Hypothetical Usecase:-
Again, ( image in quoted thread above) controlling each Elements of Frank Gehry's jumping window should be placed with a series of Offset-(X/Y).
Or vary each Element's Width / Height.

So it is a 'single-point-of-management'