I made a dynamic block with multiple parameters (linear parameter) to show different views of this joist. One criteria shows joists with different heads and the labels, another with the different heads with a leader line. I have 8 different joists with 2 visibilities for leader (on and off) so that's 16 total combinations. I put all my labels in an excel sheet and copied from there to avoid any issues deriving from typos.
Step By Step below:
(1.) I prepared the block and organized and labeled all the visibility states needed.
(2.) I assigned joist type as a linear parameter.
(2.1) The dist type is set to list and I noted 1-8 to represent all joists types required.
(3.) I assigned leader on/off as a linear parameter.
(3.1) The dist type is set to list and I noted 9-10 to represent on and off leader.
(4) I created a regular lookup to associate the joist type linear parameter to the joist type description
(5) I created a regular lookup to associate the leader on/off linear parameter to the leader on/off description
(6.) I created a double lookup to relate the parameters to the visiblity states
(6.1) First lookup in double lookup correlates both linear parameters (joist type and leader on and off) together
(6.1a) Description of the correlation matches exactly the visibility state descriptions
(6.2) Second lookup in double lookup correlated the visibility states to the description of step 6.1a
(7) BVShowed all, the regular look ups
(8) BVHid all, the double lookups
(9) Test Run
I can't figure out what is causing the "Nominal_Unit" joist type to repeat itself 3 times when selecting it on the drop down menu.
Solved! Go to Solution.
I made a dynamic block with multiple parameters (linear parameter) to show different views of this joist. One criteria shows joists with different heads and the labels, another with the different heads with a leader line. I have 8 different joists with 2 visibilities for leader (on and off) so that's 16 total combinations. I put all my labels in an excel sheet and copied from there to avoid any issues deriving from typos.
Step By Step below:
(1.) I prepared the block and organized and labeled all the visibility states needed.
(2.) I assigned joist type as a linear parameter.
(2.1) The dist type is set to list and I noted 1-8 to represent all joists types required.
(3.) I assigned leader on/off as a linear parameter.
(3.1) The dist type is set to list and I noted 9-10 to represent on and off leader.
(4) I created a regular lookup to associate the joist type linear parameter to the joist type description
(5) I created a regular lookup to associate the leader on/off linear parameter to the leader on/off description
(6.) I created a double lookup to relate the parameters to the visiblity states
(6.1) First lookup in double lookup correlates both linear parameters (joist type and leader on and off) together
(6.1a) Description of the correlation matches exactly the visibility state descriptions
(6.2) Second lookup in double lookup correlated the visibility states to the description of step 6.1a
(7) BVShowed all, the regular look ups
(8) BVHid all, the double lookups
(9) Test Run
I can't figure out what is causing the "Nominal_Unit" joist type to repeat itself 3 times when selecting it on the drop down menu.
Solved! Go to Solution.
Solved by Libbya. Go to Solution.
I uploaded the block
I uploaded the block
I don't know what caused the repeat of NOMINAL_UNIT, but when selecting the text on the lookup table, it was obvious that something wasn't right. Notice the extended blue line beyond the text:
I deleted the text and reentered it and it works fine.
Don't use lists for the input properties. There's no reason for a list and it can cause problems. No need for the move actions and invisible circles for the input properties.
I would recommend simpler names for the rows on the double lookups. At this point, I typically just use the input values, e.g. 9-1, 9-2, 9-3, etc... There's much less chance of causing an issue that way and it is more easily sorted.
Hope that helps.
I don't know what caused the repeat of NOMINAL_UNIT, but when selecting the text on the lookup table, it was obvious that something wasn't right. Notice the extended blue line beyond the text:
I deleted the text and reentered it and it works fine.
Don't use lists for the input properties. There's no reason for a list and it can cause problems. No need for the move actions and invisible circles for the input properties.
I would recommend simpler names for the rows on the double lookups. At this point, I typically just use the input values, e.g. 9-1, 9-2, 9-3, etc... There's much less chance of causing an issue that way and it is more easily sorted.
Hope that helps.
Thank you for the response! This was able to resolve my issue.
I have a question on this "Don't use lists for the input properties. There's no reason for a list and it can cause problems. No need for the move actions and invisible circles for the input properties"
If I dont do the invisible circles with parameters, what can I do instead to relate the visibility states to parameters that the lookups can control?
Thank you for the response! This was able to resolve my issue.
I have a question on this "Don't use lists for the input properties. There's no reason for a list and it can cause problems. No need for the move actions and invisible circles for the input properties"
If I dont do the invisible circles with parameters, what can I do instead to relate the visibility states to parameters that the lookups can control?
@sarahC6DTR Use a point parameter and the X and Y values of it.
Howard Walker
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
@sarahC6DTR Use a point parameter and the X and Y values of it.
Howard Walker
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
@sarahC6DTR wrote:If I dont do the invisible circles with parameters, what can I do instead to relate the visibility states to parameters that the lookups can control?
You need the parameters and you need to add them to the appropriate lookup tables, but the move actions and invisible circles have nothing to do with it. They are superfluous and serve no actual function.
@sarahC6DTR wrote:If I dont do the invisible circles with parameters, what can I do instead to relate the visibility states to parameters that the lookups can control?
You need the parameters and you need to add them to the appropriate lookup tables, but the move actions and invisible circles have nothing to do with it. They are superfluous and serve no actual function.
How do you get this table to come up so that you can enter your additional parameters?
How do you get this table to come up so that you can enter your additional parameters?
Can't find what you're looking for? Ask the community or share your knowledge.