Thoughts on Parent/Child Styles and how to implement them.

[Anonymous]

All,

I've been pouring over whatever documentation I can get my hands on
regarding Parent/Child relationships, but for some reason the 'lightbulb
hasn't come on yet'. 🙂

I understand the Parent/Child relationship... it's the how do I implement
them that is causing me grief. After creating a style that had many
variations, I thought the this would be a perfect application of the P/C
thing. So, I start looking at what else I've already done and how the P/C
thing would improve things.

Take contours for example: We have 3 scenarios in our office that we use
different 'styles' of contours - existing, proposed temporary (for E&S), and
proposed (for all other types). Within those 'styles' I have labels which
are handled differently. Slant text at one height and layer for existing,
regular text at a different height and layer for the proposed.

Would I create a style called CONTOURS, and then have children with existing
and proposed?

Line labeling is a similar thought process which is causing me to get the
extra strength Tylenol out. I imagine it would be the same for whatever
feature you are tre trying stylize.

So how are you all handling the P/C relationship or are you simply creating
431 different styles under each feature?.

...and I thought my child-raising years were over! 😉

Rick

[Anonymous]

Rick:
I am not an authority on this, but I am in the habit of creating "children"
on the fly. For instance, I had a pipe profile label that is strung out
with length, slope, pipe size along the top of the pipe line. When I found
that it was quite a mess on short runs, I created a child of that label and
stacked the above information for a "dragged" label.

Bill

"Rick Graham" wrote in message
news:5047216@discussion.autodesk.com...
All,

[Anonymous]

I'm going this route for now, and keeping an open mind to the fact that I
may have it all wrong.

.......and FWIW, Excedrin seems much better for these types of headaches. 😉

"Rick Graham" wrote in message
news:5047216@discussion.autodesk.com...

So how are you all handling the P/C relationship or are you simply creating
431 different styles under each feature?.

[Anonymous]

AND another thing that I forgot. Get in the habit of selecting the label in
your drawing and create and revise your "children" right there. Going back
to the Settings in the Toolspace is time consuming.

Bill

"wfb" wrote in message
news:5047194@discussion.autodesk.com...
Rick:
I am not an authority on this, but I am in the habit of creating "children"
on the fly. For instance, I had a pipe profile label that is strung out
with length, slope, pipe size along the top of the pipe line. When I found
that it was quite a mess on short runs, I created a child of that label and
stacked the above information for a "dragged" label.

Bill

"Rick Graham" wrote in message
news:5047216@discussion.autodesk.com...
All,

[Anonymous]

Use P/C to set the level at whigh you may want your users to be able to make
changes. If you want more stringent control then apply higher in the tree.
There may be a few instances where you would want to create children
directly. Don't bind yourself, make your system as flexible as possible. If
you make it easy for your users they should not have to create "on th fly".
It is a wash as far as the amount of styles, they are being created either
way... as parents or children.

"Rick Graham" wrote in message
news:5047216@discussion.autodesk.com...
All,

I've been pouring over whatever documentation I can get my hands on
regarding Parent/Child relationships, but for some reason the 'lightbulb
hasn't come on yet'. 🙂

I understand the Parent/Child relationship... it's the how do I implement
them that is causing me grief. After creating a style that had many
variations, I thought the this would be a perfect application of the P/C
thing. So, I start looking at what else I've already done and how the P/C
thing would improve things.



Take contours for example: We have 3 scenarios in our office that we use
different 'styles' of contours - existing, proposed temporary (for E&S), and
proposed (for all other types). Within those 'styles' I have labels which
are handled differently. Slant text at one height and layer for existing,
regular text at a different height and layer for the proposed.

Would I create a style called CONTOURS, and then have children with existing
and proposed?

Line labeling is a similar thought process which is causing me to get the
extra strength Tylenol out. I imagine it would be the same for whatever
feature you are tre trying stylize.

So how are you all handling the P/C relationship or are you simply creating
431 different styles under each feature?.

...and I thought my child-raising years were over! 😉

Rick

[mmccall]

After using C3D for 12 months now I was looking to revise my current settings for the new year based on what I've encountered trying to use my current setup. The P/C style structure was something I still didn't quite understand.

1. What control does a parent style have on the child styles?

2. Is the parent style a usable style or is it there just to control features of the child styles.

3. Can there be more levels to the structure? (grandparent/parent/child)

[Anonymous]

the biggest benefit i've seen from having p/c styles is the ability to "push" a setting (or several) through many styles at once. this shaves a great deal of time when trying to configure and manage standards.

however, i'm saying this without a whole lot of experience in using p/c styles... my opinion may change as i get deeper into setting up our standard template.

[Anonymous]

That's kind of the point for them.

I've taken the approach that a parent should control display, common text,
and other appearance related issues. The children should add in specific
components, make changes in formatting for a specific use, etc.

--
James Wedding, P.E.
Technology Manager &
Associate
Jones & Boyd, Inc.
Dallas, TX
XP/2 on P4-3.4/1G
LDT 2006 & C3D2006/SP2
www.jones-boyd.com
www.ee2inc.com