Line Style Name Question

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:

  1. Rename the line styles to remove the trailing space. We would need to determine the effect on any existing elements using the original line style names. (For consistency, we should find any and all such linestyle and fix them as well. This would also require edits to the Element Templates to make sure the renamed line styles still function)
  2. Leave the line styles as it, and fix the element templates. This would still require a significant amount of manual efforts to find any additional mismatched line style names.
  3. Add new line styles, with corrected names (removing any trailing space characters). This may result in seemingly duplicated names in many of the interface items when a user tries to select a linestyle. We suspect that would result in user confusion and would not prevent the continued use of the undesirable line style names.

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!   

Parents
  • 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.

    What happens if you use quotes around the keyin in LC="trailing spaced name style  "

    Lorys

    Started msnt work 1990 - Retired  Nov 2022 ( oh boy am I old )

    But was long time user V8iss10 (8.11.09.919) dabbler CE  update 16 (10.16.00.80) 

    MicroStation user since 1990 Melbourne Australia.
    click link to PM me 

  • I believe both with or without will work. What is happening is the Element Template seems to have the linestyle names with no space, and fail to assign a line style. If I open the DGNLIB and reassign the line styles, it then shows the line style names with the trailing space and then the element templates work. 


    Charles (Chuck) Rheault
    CADD Manager

    MDOT State Highway Administration

    • MicroStation user since IGDS, InRoads user since TDP.
    • AutoCAD, Land Desktop and Civil 3D, off and on since 1996
  • I guess I would try Option 1 first. Back up enough to put back as it was if it doesn't clear it up. Option 3 would be fine (create a new resource file), who cares if there are 2 linestyles with the same name, one with a space, users will read the name and the linestyles will be the same. Option 2 is the best solution, if it's just the Element Templates that have the issue. Fine job you've done, identifying the issue and creating solution.

    Side Note- Years ago my company did loads of work for Maryland DOT. If you were there back then you'd remember a fellow named Duane Barton. The way you guys handled contours was brilliant, 2d file with an attached Z attribute.

    Connect r17 10.17.2.61 self-employed-Unpaid Beta tester for Bentley

Reply
  • I guess I would try Option 1 first. Back up enough to put back as it was if it doesn't clear it up. Option 3 would be fine (create a new resource file), who cares if there are 2 linestyles with the same name, one with a space, users will read the name and the linestyles will be the same. Option 2 is the best solution, if it's just the Element Templates that have the issue. Fine job you've done, identifying the issue and creating solution.

    Side Note- Years ago my company did loads of work for Maryland DOT. If you were there back then you'd remember a fellow named Duane Barton. The way you guys handled contours was brilliant, 2d file with an attached Z attribute.

    Connect r17 10.17.2.61 self-employed-Unpaid Beta tester for Bentley

Children
  • 1st, that contour thing sounds like a GEOPAK capability.

    2nd, GEOPAK was bigger at the Transportation Authority (toll roads) but was used by a select few at the Highway Administration.

    3rd. While we had been an InRoads shop since it originated (as TDP) it was under watch that we brought in GEOPAK as another tool in the toolbox. Not to replace but to supplement InRoads.

    4th. Sometime after that, with 18+ years at the DOT I ventured out into the consultant world for about 21+ years and decided that before I close out my career, I'd return and steer us into ORD. Been back a little over 3 years - we are not there yet!


    Charles (Chuck) Rheault
    CADD Manager

    MDOT State Highway Administration

    • MicroStation user since IGDS, InRoads user since TDP.
    • AutoCAD, Land Desktop and Civil 3D, off and on since 1996