I´m using Civil 3D 2012 SP1
I think it a great idea to simplify the styles list. However, I'm not sure it will work out as intended. When using description keys to assign styles to imported points, how can the correct style be applied if one style has several visibility states? Maybe a solution would be to allow child styles of points and have the child styles automatically created from the visibility states of a dynamic block.
Example workflow...
Civil 3D: Warning! The selected block is dynamic block with 5 visibilty states. Do you wish for child styles to be automatically created?
User: Yes.
Civil 3D: 1 parent style and 4 child styles created. Have a nice day!
Yes, it's a good idea but are still created the same amount of point styles.
And that gives work to create a dynamic block visibilitywith different states is much larger than several blocks toassign a style for each point.
The problem is having too many styles of point withoutbenefit of dynamic blocks with several states of visibility.
I also use descriptive keys to autocroquis and a solutioncould be, for example:
If I have the key descriptive (code) = tree, and select astyle for that key point that uses a dynamic block, the tableof descriptive key cosets, to create for that code suffixes to the relevant code and associate the visible state.
For example:
code = tree separator=_
sub-code =palm visibility state = palm
sub-code =orange visibility state= orange tree
....
I create as many sub-codes(sufix) as visibility states have the block.
In the field controller, I would use the code "tree_palm","tree_orange", etc. ..
Also, if I change the description key of the point properties , then, change the visibility of mark.
Yes.
This is my last proposal, accurate
The problem is lies in that for Civil 3D styles are a form of visibilty state. So to have a style with several visibility states is like having a style with styles. Lots of chaos can ensue. That's why I proposed automatically generated child styles (or just styles).
OK.
You're right.
Anyway, it is necessary to create sub-folders in the folder "style point" to organize and store point styles in folders.
The folder "style point" can not create sub folders.
If I have many styles about different types of trees, I wouldhave a folder "trees" into the folder "style point".
You're right! Why can't one organize say for instance surface styles into various child styles categories (contours, watersheds, etc...). It seems child styles are only applicable to Civil 3D labels, not tables, not object styles, only labels.