How to rotate a nested family?

[Anonymous]

How would I rotate the pulls on the door so they are horizontal for the drawer? (see attachment)

[L.Maas · Accepted solution]

You can not. Through the way the handles are modeled they are fixed in certain planes. You could edit the workplane and choose a new host.

(in this case I chose the right side of the cabinet)

However this is a 'dirty' solution. Best way would be to remodel the handle.

If I have these kind of items, which can be in almost any position, I often use nested face based families which I than can stick on any face. Other solutions might be to separately model horizontal and vertical handles.

[Anonymous]

But I want it to change when a person changes "Pull styles" in the instance parameter. If I make horizontal pulls is there a formula I could use that would change the drawer pull if the vertical pull is changed?

[nathan.chapman]

I agree with Enllnt that your best option would be convert that level hosted handle family to face.  This will allow you to have your family type selector like you have.  Then just assign an angle parameter to the handles.  You can drive this angle a couple of ways.  One would be have the user type the angle or have a simple boolean with a yes/no parameter like below.

[Anonymous]

I don't want the end user to have control which Pulls are horizontal/vertical. I just want them to select a pull in the type selector and for all of them to change.

[ToanDN]

Use a standard or face based generic model family for your handles as @EnlIn mentioned would accomplish exactly what you want.  You can assign different rotation parameters to different handle types.  Why did you model it using a casework template in the first place?

[Anonymous]

Because I didn't want to use a generic model because I was using the lock and hinge in a generic model and I wanted it so when your in the pull type selector it only showed pulls.

[Anonymous]

@ToanDN what would you have done?

[ToanDN]

---

@Anonymous wrote:

@ToanDN what would you have done?

---

I would have done exactly what @L.Maas had suggested.

Model it as a face based generic family and nest it to the casework.  I earlier said I would use a parameter to control the rotation but I am retracting that notion.  Users should locate and rotate the handle within the casework family for each instance, as they should if they assembled the casework in real life.  A handle is a handle, you buy a load of the same type, mount them where you want them to be at any angle you want them to be.  They are still the same exact piece of hardware.

Also, a handle family needs not or should not include unnecessary constraints such as a height above floor level.  That should be controlled within the host family.

Your concern about an user may select a wrong thing from the type selector, IMHO, is over the top.  It is like this: the proper way of mounting on a horse from the left side is with the left foot on the foot rest first, to enforce this, you chop the riders right foot off so that they absolutely can't use the wrong foot, instead of educating them.