Entire Nested Swappable Family for the entire thing, not just the Profile.

Hi Aaron,

I'm mulling over the idea to build in the ability to swap out push-side & pull-side architraves independently as it's within the realm of possibility that they could be required to be different. Previously I had a single profile which encompassed both architraves and the door frame/lining and stop whereas now I'm looking to test out the door frame/lining and stop as 1No. sweep and the architrave's as 2No. separate sweeps (all are currently in the same family which in turn will be nested into the parent door family). Just so I understand your reply, are you recommending 1No. family per architrave profile type which would contain only a single sweep?

I would recommend doing the frame and architraves separately. Depending on how many architrave styles you have, I'd suggest one of these two nesting structures:

• Door Family
  • Frame Composite Family
    • Frame Component Family
    • Exterior Architrave Component Family
    • Interior Architrave Component Family
  
  
• Door Family
  • Frame Component Family
  • Exterior Architrave Component Family
  • Interior Architrave Component Family

The reason for the different nesting structure is that Family Type Parameters can't be linked in the host family. If there are many different styles of architraves, having them nested directly in the door family allows more control over them. Alternatively, if there are only a few styles, then a family type representing each can be created in the Frame Composite Family and then controlled with a Family Type Parameter.

It's the only method to keep one from growing more gray hairs sooner than later. All others would require more finesse, than simply in just 2 clicks & no data entry & done.

This is what i was suggesting/recommending. Nested Nested Family selection gets old, really fast. Especially with things as complex as Division 08.

I think the latter structure is what I'd be looking for and for the behaviour of the parent door family I'd like to select the door and have 3 family type parameter pull down menu's.

have you started nesting trim into your doors now too? I'm so behind! :hide:

The Parallax Team Window Libraries have been that way for some time. They have two additional Nested Families, compared to the Doors: EXT Trim and INT Trim. Those Trim pieces are Face Based, so they can have their own interactions with the Walls, as needed (cutr away finishes a very specific amount, etc).

We CURRENTLY haven't gone through the entire library of Doors to add them in, since its only certain types of Projects that would need it (Projects Like Old Parkland), and so far none of our current Door Library clients have asked for it.

The ONE caveat to them all being nested at the Parent level (one caveat that exists for Doors but not really for Windows) is that the Nested Frames (in my cases) actually change the shape of the opening on the whole. That means you have to think deliberately about what you want the trim to do. For instance: Sidelight sizes (in my library) arent "available" in the Parent Family. So sizing Door Trim is more complicated. *(Yes, i know HOW people make it available, i dont WANT it available, its an intentional workflow choice).

Im personally fine with that, it just means being cognizant of what will happen if you pick a Frame with a sidelight or that doesnt go down to the ground, and then you put a Door EXT Trim component on it also. The way around THAT is that you can certainly have the trims underneath the Door Frames, as kowen mentioned earlier), but if im going to do that, i almost just assume manually place the Door Trim components.

I knew your windows did that, and mine are similar; I just didn't think it was worth it for the doors, since as you mention - there are too many variations and the trim is only needed in certain types of projects. Thanks for clarifying :beer: