Detail Components - Can I schedule?

[saeborne]

Is it possible to schedule detail items? I have a sneaking suspicion that the answer is no....

Using this thread as a guide:
http://forums.augi.com/showthread.php?t=38943&highlight=EGRESS+PATH

I'm creating an egress path family. The familes shown in these examples are in the category of specialty equipment, or generic models.

However, I wanted to do it out of Detail components, so that they only show in one view. But... then do I sacrifice the ability to schedule?

Thanks in advance,

Bryan

[jeffh]

Because detail components are "drafting" items they are not something that can be scheduled.

[cporter.207875]

One thing that you could do, and it might be over-complicated, is to build shared parameters into the detail component, then schedule just those parameters. For example, you could add a shared paramter called Component, and make a text field that has the family name typed in. That way you could schedule the name of the component. Then you could schedule whatever other paramters you want to see in the schedule.

On a side note, it might make more sense to build it as a model element, then use filters to block visibility in all the views you don't want it to be seen.

[Steve_Stafford]

... into the detail component, then schedule just those parameters...Can't schedule a detail component no matter how many parameters shared or otherwise you put in it, sorry.

In the egress example I posted, in the linked thread, the family is designed to only show when the view's Detail Level is "Fine". Otherwise it shouldn't show up in "regular view". Regardless, as mentioned, a Filter should help manage the visibility. The solid sweep is easy to control via Visibility/Graphics and so is the line. It is just the nested symbol for the arrow and dot that play havoc with keeping the them hidden from other views. The arrow and dot are nested annotation symbols so they maintain their plot size regardless of view scale. If they were not then the user would have to supply a scale factor to use them. No win situation, just so close yet so far. But you can schedule them!

[cporter.207875]

Can't schedule a detail component no matter how many parameters shared or otherwise you put in it, sorry.

In the egress example I posted, in the linked thread, the family is designed to only show when the view's Detail Level is "Fine". Otherwise it shouldn't show up in "regular view". Regardless, as mentioned, a Filter should help manage the visibility. The solid sweep is easy to control via Visibility/Graphics and so is the line. It is just the nested symbol for the arrow and dot that play havoc with keeping the them hidden from other views. The arrow and dot are nested annotation symbols so they maintain their plot size regardless of view scale. If they were not then the user would have to supply a scale factor to use them. No win situation, just so close yet so far. But you can schedule them!

If you create a multi-category schedule, then hit "Add Parameter" from the Fields tab of the schedule properties, you can select the shared parameters that you built into the detail component. You are not scheduling the actual component... just the parameters. Again, a bit silly to do it this way, when filters and other graphic controls work so wonderfully for this situation, but it does work.

[twiceroadsfool]

Theres a ton of ways to make it only show in one view. Filter it out, have it only show at a specific Level of Detail, subcatagorize it (although that depends on how your family is built).

Mine is a specialty equipment family that only shows at Coarse LOD, since there is never a drawing in our set that shows the catagory at Coarse, besides that one set of Egress Area Plans...

[saeborne]

Thanks for all of the replies, fellas.

I went ahead and made it a family component, as opposed to a detail component. I used the Site category... Most of our site plans only show the roof level, so I don't anticipate any cross-over "spillage."

I do like adding the level of detail visibility parameter. I may go back and put that in.

Thanks again,

Bryan