@JBerns wrote:
@Libbya ,
That is an impressive solution to keep an array centered. You continue to inspire, Andrew.
Would you agree the solution may have been easier if dynamic blocks supported a mix of Parameters/Actions with Geometric/Dimensional Constraints?
Your solution to change visibility states with Stretch Action was very helpful.
I would ask for some more clarification on your solution if you would please?
- In the Lookup1 table, you have entries with a mix of parentheses and brackets. Is there a functional difference between a parenthesis and a bracket?
E.g. (100.0000,150.0000),(200.0000,250.0000],(300.0000,350.0000],(400.0000,450.0000],(500.0000,550.0000],(600.0000,650.0000]
- What documentation did you use to discover this double-lookup and parameter list functionality?
I am working on a stair tread and will need similar array-centering functionality. I tried using Geo and Dim Constraints, but quickly ran into problems with Parameters and Actions.
https://forums.autodesk.com/t5/dynamic-blocks/problem-flipped-objects-in-different-visibility-states...
Thank you for your continued generosity. I look forward to your reply.
Kind regards,
Jerry
Dynamic blocks do support combining constraints and dynamic parameters, but it usually doesn't work out very well. I think that in order for them to play well together the dynamic parameters/actions would need to be able to dynamically alter dimensional constraints. At this point, as a general rule, if it can be done without geometric or dimensional constraints, it is easier to do with only dynamic parameters/actions. In most cases, constraints cause more problems than they cure. There are a few special situations that can only be accomplished with constraints, but those are quite rare.
Yes, there is a functional difference between parentheses and brackets. This follows mathematical conventions exactly for range values. Range values take the form of a beginning bracket/parenthese, a value, a comma, a higher value, and an end bracket/or parenthese. The two values are the extremes of the range. The range includes all values between the extremes. If a bracket is used next to a value, the value is included in the range. If a parenthese is used next to a value, then the value is not included in the range. If you have a range value that only has one value and a comma then the range includes all values in the direction of the missing value. In other words, the range value of [12,) would include all values greater than and equal to 12. A range value of (12,) would include all values greater than 12 (it would not include 12). Most of my understanding of dynamic blocks and more specifically lookups and double lookups comes from experimentation. There is some info on the single lookups and range values in the AutoCAD help and it is helpful but contains several errors.