More than one Visibility State in a Block
Currently it only lets me have one visibility state in a block.PLEASE tell me there is some way to work around this?
The example I have is basic.I have a 6"-nominal wall in plan consisting of 3 lines, (2)extents + (1)centerline, each 1" long.Stretch parameter let's me make the wall longer.
At the end of those 3 lines are 3 more lines.a 6" line extending each of the wall-extents line, and a 3" line extending the centerline.I have a visibility state that allows me to turn on-or-off each of the 6" extensions.Turning off one extension leaves a 45%%d miter to the wall (left or right) for instersections.Turning off both of those extension lines creates a "Tee" situation.
Now... I'd also like to be able to add a SECOND visibility state for various hatchings.I want to be able to add insulation batting, solid hatch for fire-rated walls, or other misc. hatches for special scenarios such as 'gas tight' or 'fire resistant' walls.
Is there any way to have separate Visilbity states to control that? You can probably accomplish it with a LOOKUP TABLE.I messed around with them a while ago - I'll have to check if I have those blocks again. Couldn't find the block, but found this thread.
Yea I was reading through that... Saw Cory's post in the Autodesk Discussion Groups helping someone else with a similar issue, and eventually linked back to that thread... but I guess I had trouble following it's logic or seeing how it'd fit for my example.
I'm very inexperienced with the Lookup dealio, so I'll start reading about it and trying some things and find out. Can you post what you have now and also what you want to include in the block?I _think_ I understand what you want to do but.... OK, the basics of this are that you will need to create a visibility state for every combination you want to show.Also create a visibility state for each catagory of states (i.e. hatched, not hatched).
Then create a lookup table that points to the "catagories" (i.e. hatched, not hatched, etc)
This will point to the"root" visiblity states your created.
In these root visibility states you will have a lookup table in each that points to all the visibility states you want to be able to select from for that catagory.
Do that for each catagory and then go back and delete only the grip for your visibility state action.
it will be easier to learn to use bvshow and bvhide at the command line to manage visibility for objects then the hide show buttons.
Its confusing at first, but not too hard. After looking through the help file on 'lookup parameter' and seeing how Mr Cory's example block worked in the thread Matt linked...
...I see how to do it.
I currently can think of 3 possible hatchings, maybe 4, so combined with 4 end-wall-treatments (not counting the "ALL SHOWN" I always put in my blocks) that's gonna be a PITA to make.
BUT.It will be worth it in the end, I think, and I currently have some time to spend making the block.
Thank you Shiny, Matt, and (even in absence) Cory. Heres a pretty simple version of how I do it. I'm losing it.
I had everything set up.
I have the lookups set up.
The execution fails though.
I can't see how to be able to make one Lookup be "left / right / end / tee" and the other be "solid / ansi31 / insulated / no hatch" and have it somehow add those together to make "Left - Solid" or "End - Insulated" from the 2 Lookup selections.
Block progress attached: OK, you can't "stack" the visibility states, rather you have to use them so that you select one first, then the next.
I see what you mean by a single state, for what your after, that is your limitation.
lookup tables are an "OR" not an "AND"
you would have to have one table (say for the hatching) that the user selects,
THEN they would select the configuration options.
you need to reference a seperate state for every combination.
页:
[1]
2