Dynamic block: parametric constraints plus array

Dynamic block: parametric constraints plus array

Jessypaixao
Enthusiast Enthusiast
1,918 Views
2 Replies
Message 1 of 3

Dynamic block: parametric constraints plus array

Jessypaixao
Enthusiast
Enthusiast

Hello, I have managed to make the two blocks attached in the drawing, but I cannot for the life of me merge the behaviours of the two blocks. The first block is parametric and the dimensions of the objects change as listed on the block properties. The second block grows in modules with the array action parameter.

 

Is there any way I can accomplish both behaviours within the same block?

0 Likes
Accepted solutions (1)
1,919 Views
2 Replies
Replies (2)
Message 2 of 3

Libbya
Mentor
Mentor

I believe that you can accomplish all of the desired behavior using only dynamic parameters/actions, but that you cannot accomplish it using parametric constraints.  You can accomplish all of the individual parameter list values using linear constraints and stretch actions.  You can accomplish the arrays in the manner you did so but will need to duplicate all of the items in individual visibility states for each array column offset.  You can use a double lookup to switch the different array column offsets.  You can use the parameters that affect the column offsets on the input table and use visibility states on the output table.  I started to make a video but was 8 minutes into it and only getting started and decided I didn't want to spend the time it would take.  If you need further explanation or get stuck, let me know.

0 Likes
Message 3 of 3

Jessypaixao
Enthusiast
Enthusiast
Accepted solution

Yes, I understand the logic behind your answer, but I was actually trying to avoid having to use the visibility states as it complicates any change I may need to make to the block in the future and restrict things more than I wish to (not to mention confuse the heads of some of my coworkers...).

 

I was trying to see if the work of joining it all together was worth the gain, but it seems that for now a more simplistic approach is still the best "cost/benefit" for our team. I appreciate the suggestions though. I will keep them in mind the next time I am looking to improve processes.

 

For now, I'm gonna stick to simple arrays of separate constrained blocks, as such:

Image.png

 

If anybody else finds a solution that doesn't involve several tables and visibility states, I am all ears. 😄

0 Likes