ron.sanpedro
2007-12-05, 10:27 PM
There are OOTB Line Patterns of various Dashed and Hidden flavors. Some of these have names that I have problems with; like Loose, what the @$#% does “loose” mean? A bowel can be loose, a sketch can be loose, but a line pattern? ;) Also, the naming convention is a mix of both “descriptive” names like Dashed, and “use” names like Hidden. Seems to me that Line Patterns should be descriptive only, and use is addressed elsewhere, to whit…
There is duplication of Hidden lines under Line Styles. Not only do you have the hard coded <Hidden>, you have the user editable Hidden Lines. And OOTB they don’t even use the same Line Pattern! Just begging for inconsistent graphics.
My thought is to delete Hidden Lines, and just use <Hidden> when I need a Hidden line, be it a Drafting Line, a Model Line or an override with the Linework tool. I then use the same Line Pattern for all Hidden Lines subcategories and I have a nice consistent representation throughout the project, no matter how I get to a Hidden Line, I get the SAME hidden line.
.
In a similar vein, I have a problem with having Line Style names of Thin Lines and Thick Lines, then having Detail Items subcategories of Heavy Lines and Light Lines, while repeating Medium Lines! Aiii. Why not just use Thick Lines in both? Doesn’t consistency count for anything? But on this one I worry that there may be a ton of content already built that uses the Heavy and Light categories and I am stuck with inconsistent naming. Why oh why can’t the templates and OOTB content be, oh I don’t know, “Internally Consistent”?
Anyway, rant mode off. Anyone else…
1: Feel like this stuff should be rationalized OOTB?
2: Done any of this and found it to work well, or have problems?
Comments?
Thanks,
Gordon
There is duplication of Hidden lines under Line Styles. Not only do you have the hard coded <Hidden>, you have the user editable Hidden Lines. And OOTB they don’t even use the same Line Pattern! Just begging for inconsistent graphics.
My thought is to delete Hidden Lines, and just use <Hidden> when I need a Hidden line, be it a Drafting Line, a Model Line or an override with the Linework tool. I then use the same Line Pattern for all Hidden Lines subcategories and I have a nice consistent representation throughout the project, no matter how I get to a Hidden Line, I get the SAME hidden line.
.
In a similar vein, I have a problem with having Line Style names of Thin Lines and Thick Lines, then having Detail Items subcategories of Heavy Lines and Light Lines, while repeating Medium Lines! Aiii. Why not just use Thick Lines in both? Doesn’t consistency count for anything? But on this one I worry that there may be a ton of content already built that uses the Heavy and Light categories and I am stuck with inconsistent naming. Why oh why can’t the templates and OOTB content be, oh I don’t know, “Internally Consistent”?
Anyway, rant mode off. Anyone else…
1: Feel like this stuff should be rationalized OOTB?
2: Done any of this and found it to work well, or have problems?
Comments?
Thanks,
Gordon