PDA

View Full Version : keep readable thru nested families?



cadman6735
2009-06-10, 03:29 PM
I am creating an electrical library for our MEP guys.

I have created the symbols as an annotation family then nested the annotation symbols into the desirable electrical family.

When I load the desired electrical family into a project everything works as it should except for the readable text.

The text rotates with the symbol when hosting the electrical family to a wall.
When hosted to the north side of a wall it looks perfect.
When hosted to a west side wall the letter is facing the wrong way, away from the border title.
When hoted to an east side wall the letter is facing towards the border title (which is fine)
When hosted to a south wall the letter is upside down.

The keep readable is checked and in some case I even pushed the varable check box thru from the annotation family into the electrical family (thinking it was because it only goes one deep in nested families.) This did not work.


My desired out come would be to have the letter facing one direction all the time.

What am I missing?

Thanks

aggockel50321
2009-06-11, 12:39 PM
Take a look here. (http://forums.augi.com/showthread.php?t=102020)

clog boy
2009-06-11, 01:31 PM
The symbol in the family will rotate with the family.

One work-around is to place one instance of the symbol upright, and assign a visibility instance parameter to it. Then place an inverted symbol on top of the upright symbol and assign a visibility instance parameter to it.Then do the same for left and right positions, if you choose.

Once placed in the project, you can then control the symbol's rotation by checking the appropriate instance parameter check-box.

Another method would be to leave the symbol out of the family, create a tag, and just tag the devices. You'll then be able to control it's position as well.

I would go with the second option. But as workarounds go the first option really isn't a bad one. The reason that I wouldn't prefer it is that you can always forget to check or uncheck a box. Another reason is when you use it in groups, instance parameters can't be different throughout groups.

For instance I have once created a box that could be anything: a cooker, a dishwasher, a microwave, you name it. Just amend the nested label and be done with it.Same thing happened. So I created a label for it.