Dynamic Block Stretch + Array

[Anonymous]

Hey Guys,

First post, been creeping in the shadows for a while. Anyways, I started messing around with dynamic blocks recently to improve my productivity, and it appears that I've hit a wall, I usually start a block then add dynamic properties to them as I need them. The idea I'm after is that I have a block which can stretch to min or max distance, but then if I want too I can have the stretched object arrayed anywhere from 1/2" to 1 inches away from the previous block. Any ideas on how to do this? One other issue I found that when I select the block attribute definition (A in the case of the attached file), it doesn't want to array it for some reason. I feel like someone has done it before, but I just haven't been able to find anything that correctly describes what I'm after.

The short description of what I want it to do.

Stretch Min = N/A Max 60" (I know that this need to just be set as a parameter in the stretch command just haven't gotten around to it)

Rotate the block and attribute separately (I already have this done so I'm hoping it can just modify the selection to work with the array once I have that figured out)

Array the stretched blocks at an increment of 1/2"-1" from the previously stretched portion separately.

In the future I would also like to add a dimension to this with two - three visibility filters where the first stretched block shows the dimension and adjacent gap but misses it for the remaining items except for the last gap and panel. Also maybe an overall dimension fo the entire block associated with the array. Maybe you guys could point me in the right direction to a write up where I can find out how to do this in more detail.

Thanks in advance for any help you guys could provide.

[j.palmeL29YX]

The "rotated dimensions" are created with the DIMCONSTRAINT command (or any of its "Sub commands"). They fix the dimension (size) of a geometric object. These dimensions are not visible and not editable in block references. 

The "parameters" are created with he BCPARAMETER command (or any of its "Sub commands"). They are available only in the block editor. They also drive the dimension (size) of a geometric object. But they can have grips and their value can be changed in blockreferences (via the grips or by typing a value in the properties panel. 

Additional you may read my last post in the thread >>How would you make these into a single curve block?<< from some day ago (2025-03-13).

[bradley_minger93J6Y]

Hi again,

First I want to say thank you for all your help. You've been very informative and the block you provided is excellent. I read your other post and understand that I cannot use AP and DCP at the same time. Almost all the blocks I use are controlled exclusively with DCP, however I've been using DCP's to fix geometry that I never intend to move and I suspect that it's slowing down my blocks/drawings. Based on your block I have two questions.

1. Are dynamic rotated dimensions more computationally efficient than DCP's?

2. How do I show and edit the dynamic rotated dimension once it's placed inside a block? In the example block you gave me, the dimension controlling the hole offset from the edge is only visible when I click on the line while editing the block. Is this the default behavior?

[j.palmeL29YX]

to 1: 

Generally is to say, that blocks which are controlled by constraints decrease the performance during handling with a dwg-file. I can not say if this is caused by the Parameters (the dimensional constraints) only or if this slower performance is caused by the geometrical constraints (or both). Whenever possible you always should prefer Dynamic Parameters and Actions (AC). Only if you can not solve the desired functionality this way you should consider to solve functionality using constraints (DCP) - and live with all their disadvantages 😉 . 

to 2: 

You have access to these rotated dimenions only in the block editor. They are used to fix the size of geometric objects that should not or may not be changed by the user of the block. Therefore they are per default invisible in the block references. 
You can enable the visibity of these dimensions in the blockreference by changing their property "Constraint Form" from Dynamic to Annotational.

Their look now follows the assoziated dimension style. But you only can SEE the value, it is in the block reference not editable.