I just discovered, we have a few linestyles that have names that end with a space character. During a LC= Key in, MicroStation will try to locate a best match and if there is any ambiguity, open a list dialog box, and if there is not, activate the matched linestyle.
However, in the Element Templates dialog box, you cannot actually key in a linestyle name. What I have learned, is that some line styles in some element templates are missing the space. I'm not sure how this occurred, but the end result is if the stored line style name does not match exactly, the element template will not set that linestyle. It will set everything else defined in the element template, however.
We have hundreds, if not thousands of files in ProjectWise expecting one of our to specific workspaces to correctly display its contents. So I cannot implement a simple fix without knowing the repercussions of any fix that involves existing files.
My choices seems to be one of the following:
does anyone have any thoughts or suggestions on our dilemma?
Oh how I wish the V8 Level naming committee, all those years ago, would have listened to the handful of us who advocated for ByLevel Symbologies!
I think you have to go with option 1. Either of the other two options you're just prolonging the agony until you fix it correctly.
While you're having to go through all of this, now is an opportune time to revisit using ByLevel symbology for everything. Maybe a new committee will see the error in their ways.
Check out the Batch Conversion tool to remap from the old line style names to the new line style names in all of your files. Not sure if it will honor the trailing space in the line style names when doing the comparison, but will help tremendously if you have to edit all of your dgn files.
We had a similar issue years ago with a client that added an extra space on the end of their font name in their InRoads XIN file. None of the text was coming out correctly. That was a minor fix compared to what you're up against.
I wish you luck.
Rod WingSenior Systems Analyst
Here's where we stand.
A lot of files use this linestyle - some no longer active. Most are in our original V8 Workspace which use common level names across disciplines for different purposes and with many different symbologies. These pretty much ruled out ByLevel symbologies. However, as with many of our linestyles, these are used for both our original V8 workspace and our current workspace.
When we began working on our current workspace for Ss4 (now Ss10), we revisited level names and went with an NCS compliant approach. We were actually restoring the discipline character by doing this, as that infamous committee based their levels on an NCS "like" approach, but decided that since the CADD file names were discipline specific, we did not need a discipline designation.
Unfortunately, our resources are stripped really thin. Right now, I'm a one man band. So while we are gradually introducing ByLevel into the workspace, it is not being done in a very timely manner. Ad there is a lot of compromises and book keeping to accomplish it correctly.
So this fix will have to wait for Open Roads Designer CONNECT Edition. We know a lot of things need to change for it, so it will be easier to ensure such things are addressed.
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration Maryland DOT - State Highway Administration User Communities Page