DBs in riser diagrams

[cwjean76]

I'm attempting to set up a DB(with several fire alarm symbols) to utilize in a riser diagram. I've set it up with an array action, which works fine with two exceptions:

(1) As it arrays, it doesn't allow me to select each independent symbol to change it as needed. Only the first symbol has the visibility node available to change the symbol and when you do change it, the entire line of symbols change as well.

(2) Also, the array action only is available to me in one visibility mode. Do I need to set up an array up for each separate visibility mode?

I've attached the block for anyone interested in helping me understand what it is that I'm doing wrong here.

[Chris.N]

I'm attempting to set up a DB(with several fire alarm symbols) to utilize in a riser diagram. I've set it up with an array action, which works fine with two exceptions:

(1) As it arrays, it doesn't allow me to select each independent symbol to change it as needed. Only the first symbol has the visibility node available to change the symbol and when you do change it, the entire line of symbols change as well.

(2) Also, the array action only is available to me in one visibility mode. Do I need to set up an array up for each separate visibility mode?

I've attached the block for anyone interested in helping me understand what it is that I'm doing wrong here.

(1) that's because the array geometry's "source" is controlled by the visibility, the visibility itself does not. you change the source objects, you change the whole array. this might be a good example of where "nested" DB's would be handy. you can array to the Qty you need, then explode to modify each instance as required.

(2) select the parameter, r-click, object visibility, "make visible all states"

[cwjean76]

(1) that's because the array geometry's "source" is controlled by the visibility, the visibility itself does not. you change the source objects, you change the whole array. this might be a good example of where "nested" DB's would be handy. you can array to the Qty you need, then explode to modify each instance as required.

(2) select the parameter, r-click, object visibility, "make visible all states"

Thanks, Chris. Doing this made it react just the way I wanted it to. Question: Is it possible to do this w/o having to explode it?

[Chris.N]

Thanks, Chris. Doing this made it react just the way I wanted it to. Question: Is it possible to do this w/o having to explode it?

you're very welcome! one thing i'd add tho is a snap to your linear parameter for 6' increments. (properties palette)
nope, it's a popular wishlist feature, tho!

[redbullsuzuki]

Thanks, Chris. Doing this made it react just the way I wanted it to. Question: Is it possible to do this w/o having to explode it?

Could you not just array in steps, ie. 3 of these, then 2 of those, back to another 4 of the other, ie. seperate insertions of the DB...
I'm having a similar problem with a DB for doing pipework schematics...
I can set it up to switch between various outlet types, no problem, and array out to 10no. of each...
Then I started thinking about those time when I need to go left, as well as right, off the main pipework drop, or put various valving arrangements on the various branch pipework...
It starts building up into a large matrix of possibilities...
I'm settling for creating nested DB's, that may, or may, not satisfy all scenarios...

Ah well, maybe eventually all things to all situations...