My company is facing a "Hattfields and McCoys" discussion on ctb files and their usage. I would like to know which version most cad managers are employing. I am attempting to present it without bias, so I can get unbiased feedback.
One side of the argument wants to leave all drawings in a "standard" set of colors, and adjust the ctb files on a per-project or even per-drawing type basis to allow lines to be differentiated by lineweight/screening. So in a given drawing, a line that is colored yellow might plot as the darkest, thickest line, whereas in another drawing, the same line may plot as a light, screened line that is barely visible. If an individual decides a line needs to be darker/thicker, they are to adjust the ctb file as appropriate.
The other side of the argument contends that a set of standardized ctb files should be used, such that a yellow line always plots the same. If a change to lineweight is desired, the user would select a color that plots, based on the ctb file, darker/thicker/etc.
I would like to hear from both sides. Thanks in advance for your input!!
Big mistake to allow individual users to edit and change CTB file settings: Bob like yellow to be 0.1, Robert like it 0.15, Bobby like it at 0.2 when printing and 0.25 when plotting. Which standard are the other project team members Tom, **** and Harry to follow?
Sounds like you folks are ready to move away from CTBs and into the realm of STBs: screen color matter little, actual setting is done BYLAYER (or other choice you all determine) and everyone who touches the file gets the same line weight for yellow changed by one of your users.
STB: make the change. And no one is ever allowed to change it's settings, Company Standard means COMPANY STANDARD from now on.
If you're going to have lineweight by color be the company standard, then it has to be the company standard; a set of ctb files (which can always be added to on a per project basis if absolutely needed, but that standard set never gets modified by the rank and file users) designating color a = lineweight b *always*.
Anything but that is simply crushing efficiency in the workplace.
... just don't forget to send the STB along with the file. Its possible to get a drawing third-hand without a matching STB (document control usually has no idea what to do with supporting files), using styles like "BOB" "STYLE_1" "STYLE_2" etc., and have *zero* idea on how it is intended to be plotted. At least with colors you can visually identify which items are intended to plot the same style.
Yes, because changing "just because" is a really good reason to revamp your entire way of doing things... :-\
If CTB's work for you, and users like to see "yellow = .010 always" then keep with it.
If you don't care if color=lineweight, then you could think about switching. Don't ever do it just because someone claims "it's so 1990's", that mindset will get you nowhere good.
CTB is soooo 1990's
Change to STB (named plot styles)
Did anyone read the OP's actual post? First one way at the top. I'll summerize:
More than one user wants color Yellow to be different line widths: per DWG in a set and/or per project set of DWG files.
You can't do that with one CTB file andf still maintain anything resembling office sharable content for eeryone to us, but you can with one STB file. Regardless of 1990s comment or not, we should help the OP present a solution(s) to their team for consideration, not to fog up answers with pointless/vague personal feelings about doing it one way or the other
Ghee guys...............sorry about the 1990's comment. Didn't mean to hurt anyone's feelings.
In my humble opinion CTB plot styles are very restrictive and STB plot styles are much more versatile.
The OP can accomplish what they want using STB plot styles, they can't with CTB.
And I know this is an age old argument and I don't mean any disrespect to users who want to stick with CTB plot styles.
I work in a small office with about 10 users.
Half (my half) uses STB and the other half uses CTB.
And why is this you may ask?
Because the other half just doesn't want to change.
My half also use Architectural Desktop and Revit.
The other half don't, again because they don't want to change.
The other half did upgrade last year from autocad 2006 to 2012 (in the classic mode of course!!)
Where consistency is important, that restriction can be useful in keeping things inline
I agree, consistency and standards in a multi user environment are very important.
We have (our half) all agreed on the STB plot styles.
And we allow for overrides in particular projects.
Overrides are easier with STB as our basic STB files does not get changed.
All these overrides have already been defined in out standard STB file.
Access a broad range of knowledge to help get the most out of your products and services.
Start with some of our most frequented solutions or visit the Installation and Licensing Forum to get help installing your software.
Upgrading to a 2015 product? Make sure to check these out 1st!