Change Visibility State w/ Multiple Distance Parameters

Change Visibility State w/ Multiple Distance Parameters

Anonymous
Not applicable
1,895 Views
9 Replies
Message 1 of 10

Change Visibility State w/ Multiple Distance Parameters

Anonymous
Not applicable

I'm wondering what the best way to go about this is... I'd like to be able to use the distance attribute grips to change the visibility/location of blocks depending on the distance. I'd like to have only the distance grips visible and get away from selecting from a visibility list.

 

I've attached what I've come up with so far and I'm wondering if I'm on the right track or if I should go about this a different way. There's a possibility of 64 choices so I don't want to put in the effort if I'm completely off base.

 

Any and all insight is much appreciated - Thank you!

 

EDIT: I'd like to keep the blocks inside the original block dynamic as I use a block counting program that spits out a material list after exploding the original block.

0 Likes
Accepted solutions (1)
1,896 Views
9 Replies
Replies (9)
Message 2 of 10

Libbya
Mentor
Mentor

You can take an easier approach than that.  You can eliminate all of the visibility states and lookups.  Instead of having nested blocks, place your linework/text directly in block editor.  Change your text to attributes.  Use a block properties table to write the attribute values based on the distances.

0 Likes
Message 3 of 10

Anonymous
Not applicable

That would work, however I should have mentioned I'd like to be able to count the dynamic blocks after they are placed. The original block, of course, would have to be exploded, but we have a count program that spits a material list to a .CSV file depending on the block name.

0 Likes
Message 4 of 10

h_s_walker
Mentor
Mentor

You didn't need your three lookups. A double lookup will do what you want. 

See the attached image. You can turn off the lookup arrow and you can turn off the properties of the lookup as well.

Forgot to mention you can turn off the visibility arrow as well

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.

EESignature


Left Handed and Proud

0 Likes
Message 5 of 10

Libbya
Mentor
Mentor

In that case, as hwalker states, use a double lookup.  Use the two distance parameters as inputs on the one table.  Use the second table for the visibility states.

0 Likes
Message 6 of 10

Anonymous
Not applicable

hwalker, I wasn't able to see your image - ?

 

I feel like I'm close in figuring this out... Still having issue in changing the visibility states using the Distance Attributes however.

 

 

0 Likes
Message 7 of 10

Libbya
Mentor
Mentor
Accepted solution

The problem switching is because your Distance1 and Distance2 parameters are not drawn correctly to 1'-11 5/8" despite properties saying that is the dimension.  If you increase the luprec system variable to 8 you will see the discrepancy, but even the 159/256 displayed is rounded and it is off from that value.   Easy fix.  Just select the two parameters, go to properties, and  enter the correct value of 1'-11 5/8" into the distance field.  It will work after that, including 'custom' being gone from the lookup lists.

0 Likes
Message 8 of 10

Libbya
Mentor
Mentor

 

0 Likes
Message 9 of 10

Anonymous
Not applicable

Fantastic - That did the trick!

 

Thank you very much!

0 Likes
Message 10 of 10

h_s_walker
Mentor
Mentor

I didn't post an image. I attached the drawing.

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.

EESignature


Left Handed and Proud

0 Likes