Trying to create a combination stretch-array setup for window mullions inside of a window family so that I can change the number of mullions in each direction, as well as the size of the window itself, all in one family. I've done this kind of stretch-array before with louvers on an overhang, using formulas to relate the Total Width, Array Spacing, and Array #. I'm trying to do the same thing here, but am unable to set a parameter for the Array # of mullions - there's no option to add a label. Is this a limitation of the window family type? Do my mullions (currently generic face-based) have to be a different family type? What's the hang up?
Thanks
Gelöst! Gehe zur Lösung
Gelöst von barthbradley. Gehe zur Lösung
You are going to need to change your Muntin family too. In order for it to work in an Array, it has to change length in only one direction. In other words, align and lock the left end of the muntin to the intersecting x and y Origin Ref. Planes, the pull a labeled dimension from end to end. It's problematic, as an Array element, when each side lengthens or shortens equally from the center.
Thanks for the clarification on (the lack of) limitations w/in the window family type. For some reason, I cannot get that Label dropdown to show up in my window family.
After some further reading, I think the problem might be that I need to nest the Muntin family (#1) into a separate Array family (#2) to do the array, and then nest that Array family into the final Window family (#3). Does this sound right? If so, can you clarify why the array needs its own family to work parametrically?
Thanks
@Anonymous wrote:
After some further reading, I think the problem might be that I need to nest the Muntin family (#1) into a separate Array family (#2) to do the array, and then nest that Array family into the final Window family (#3). Does this sound right? If so, can you clarify why the array needs its own family to work parametrically?
The array DOES NOT need its own family to work parametrically. But, most our families do have the muntin grid Array as a separate family -- mainly because we nest the muntin family as a component into other families.
...as I understand it, the issue isn't that you can't Array; it's that you can't Label the blue Array Number Dimension. Is that correct. I agree that it is sometimes challenging "grabbing" the line underneath the number. It sounds like that is the problem; not the Array per se.
@barthbradley Thanks for your insight. Can you elaborate on why it is necessary to create the Muntin family this way in order for it to work in an array? What about doing it the other way breaks in an array and why?
Can you explain in general the difference between (a) locking the faces of an extrusion to a labeled dimension, (b) locking the sketch lines of an extrusion to a labeled dimension, (c) locking the faces of an extrusion to a ref. plane and then locking the ref. plane to a labeled dimension, and (d) locking the sketch lines of an extrusion to a ref. plane and then locking the ref. plane to a labeled dimension?
Thanks for your time
Oh jeeeez, now I feel stupid - I was thinking that label dropdown would pop up on clicking the Array number. Works just fine when I do it right, thank you!
Hey @Anonymous, don't feel bad; we have all be there. Like I said, it is challenging sometimes grabbing that line so you can label it. Glad you succeeded finally.
Regarding your other questions, let me just say it is always better to align and lock geometry to Ref. Planes, and pull your labeled dimensions between Ref. Planes. And, it is not a great idea to pull labeled dimensions between sketch line in sketch mode, primarily because those labeled dimensions are not visible outside of sketch mode. They are hidden.
FWIW
![]()
Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.