We've now got some well behaving nested window and door families, that do pretty much everything we desire of them, except appear in legends . . .
The host family is wall based (window or door type), and comprises the reference planes, voids, sills etc (everything to do with the wall interface).
The nested families (frame, sash, mullion) are shared Generic Model components.
We have used Generic Models for the nested families as they do not schedule as doors / windows, they can't accidentally be tagged as doors / windows, and because they cut nicely in plan views (means we don't need to mess around with line representation of geometry).
The problem, as above, is that they will not appear in legends, which is where we prepare the graphic description of our window / door "schedules".
We've done some experimenting and found that if the nested families are not shared, the family can be shown in a legend, and scheduling works fine, but each family becomes unique (not made out of subcomponents) creating unnecessary duplication in the database, and the nested family components don't cut in plan requiring additional linework at course / medium / fine levels (which is otherwise un-necessary).
Has anyone else discovered problems with nested families in legends?
Is there a logic behind it, or is this a bug?
Crispin