DETAILING SYMBOL STYLES

Coming to grips with the DV annotation styles, this is my current understanding of this and I am looking for feedback to know if I'm on the right track...

Not sure if the defaulting to the active Dataset's dgnlib is a bug or a faulty setup...Overall seems to work OK, I find that changes to the component models and/or to the styles library need restart before taking effect.

The Detailing Symbol Styles dialog box provide a management interface for a library of styles.

These styles rely on:

-          a set of annotation components located in the file DetailingSymbolStyles.dgnlib – this file name and location are controlled by MS_DETAILINGSYMBOLS_CELLLIST.

-          a style library within the drawing seed file DrawingSeed_Architectural.dgnlib . Each style within the library functions as a set of symbology overrides applicable to each annotation component in the DetailingSymbolStyles.dgnlib. These components are also grouped to form the cells that will be used by the various DV tools and DV processing.

The default location for the library is the active dataset’s dgnlib folder DrawingSeed_Architectural.dgnlib which is also the DV Drawing Seed file.

If ATF_DRAWINGSEED_DGNLIBLIST and MS_DRAWINGSEED_LIBLIST   specify a new location/name, the library still defaults to the active dataset’s location.

Either renaming or removing DrawingSeed_Architectural.dgnlib  from the active dataset’s dgnlib folder will render the new location defined in ATF_DRAWINGSEED_DGNLIBLIST and MS_DRAWINGSEED_LIBLIST active in terms of the Detailing Symbol Styles library.

A Detailing Symbol Style may be assigned to each view in the DV drawing seed either through the View Attributes – View Seed Options /General tab or through the View properties/General tab. This then provides for a complete seed-based DV workflow (including the DG items annotation via drawing rules, won't talk about that in this post).

When a view is processed into a drawing and when using callout tools, the library symbols cell components and their symbology are used automatically. The symbology is set either from the Detailing Symbol Style library settings or from a local copy of the library styles. Any local copy can either be different or re-synchronized at any time with the library item.

Parents
  • ChrisRev,

    I hope others are reading this thread you started, you've got excellent information.

    Yes, MS_DETAILINGSYMBOLS_CELLLIST defines the DGN library containing the cells used by the Annotate Composition Tools, the cells being individual 2D design models in the file. The default is the file DetailingSymbolsStyles.dgnlib. It also contains Detailing Symbol Styles. In the default file are the styles Building Section, Default and Detail Section.

    I think you might want to look at defining MS_DETAILINGSYMBOLS_CELLLIST and ATF_DRAWINGSEED_DGNLIBLIST.

    In made this screen capture from the example project file S-Grid.dgn (an example of a file that has no local detailing styles). As I hover over the list, I see the tool-tip that shows me which DGN library file contains the style. (Note the "unfilled" book icon indicates a library style).

    It's the same thing you see in the Text and Dimension Style dialog boxes.

    Let's say I want to use my own detailing cells and styles on a project. I set up a sample project (I'm using the structural discipline as my example). Copied over DetailingSymbolStyles.dgnlib and  DrawingSeed_Structural.dgnlib into my project's ...\support\dataset\dgnlib\ folder and renamed them with "_My." in the name: _MyDetailingSymbolCells.dgnlib and _MyDrawingSeed_Structural.dgnlib.

    I added these lines to my .pcf file:

    MS_DETAILINGSYMBOLS_CELLLIST = $(PROJ_DATASET)dgnlib/_MyDetailingSymbolCells.dgnlib

    STF_DRAWINGSEED_DGNLIBLIST = $(PROJ_DATASET)dgnlib/_MyDrawingSeed_Structural.dgnlib

    Notice I an using the equals sign "=". So it overides any previous setting for those configuration variables.

    I edited the cell-model names to all start with "My_..." and edited My_SectionLineWing cell to be a triangle instead of a rectangle.

    In _MyDetailingSymbolCells.dgnlib, I created a new Detailing Style named "My Detailing Style" set all the cells to use the cells named "My...", and changed colors to color "0" and line weights to line weight "2". And set the Section Callout Tail Wing to  use "My_SectionLineWing" (the triangle).

    My last step is to open _MyDrawingSeed_Structural.dgnlib and set the saved views to use "My Detailing Style".

    Ready to use my section cut!

    I select the Place Section Callout tool and set the Drawing Seed to Struc - Framing Section, which is using "My Detailing Style", and place my section. It has the triangle on the wing terminator and is weight 2 and color 0 (black on my white background).

    To see what all the Properties in the detailing style are controlling look at this in the Help Contents:

     Help > Contents > MicroStation > Menus > Element Menu > Detailing Symbol Styles

    Hope this helps.



Reply
  • ChrisRev,

    I hope others are reading this thread you started, you've got excellent information.

    Yes, MS_DETAILINGSYMBOLS_CELLLIST defines the DGN library containing the cells used by the Annotate Composition Tools, the cells being individual 2D design models in the file. The default is the file DetailingSymbolsStyles.dgnlib. It also contains Detailing Symbol Styles. In the default file are the styles Building Section, Default and Detail Section.

    I think you might want to look at defining MS_DETAILINGSYMBOLS_CELLLIST and ATF_DRAWINGSEED_DGNLIBLIST.

    In made this screen capture from the example project file S-Grid.dgn (an example of a file that has no local detailing styles). As I hover over the list, I see the tool-tip that shows me which DGN library file contains the style. (Note the "unfilled" book icon indicates a library style).

    It's the same thing you see in the Text and Dimension Style dialog boxes.

    Let's say I want to use my own detailing cells and styles on a project. I set up a sample project (I'm using the structural discipline as my example). Copied over DetailingSymbolStyles.dgnlib and  DrawingSeed_Structural.dgnlib into my project's ...\support\dataset\dgnlib\ folder and renamed them with "_My." in the name: _MyDetailingSymbolCells.dgnlib and _MyDrawingSeed_Structural.dgnlib.

    I added these lines to my .pcf file:

    MS_DETAILINGSYMBOLS_CELLLIST = $(PROJ_DATASET)dgnlib/_MyDetailingSymbolCells.dgnlib

    STF_DRAWINGSEED_DGNLIBLIST = $(PROJ_DATASET)dgnlib/_MyDrawingSeed_Structural.dgnlib

    Notice I an using the equals sign "=". So it overides any previous setting for those configuration variables.

    I edited the cell-model names to all start with "My_..." and edited My_SectionLineWing cell to be a triangle instead of a rectangle.

    In _MyDetailingSymbolCells.dgnlib, I created a new Detailing Style named "My Detailing Style" set all the cells to use the cells named "My...", and changed colors to color "0" and line weights to line weight "2". And set the Section Callout Tail Wing to  use "My_SectionLineWing" (the triangle).

    My last step is to open _MyDrawingSeed_Structural.dgnlib and set the saved views to use "My Detailing Style".

    Ready to use my section cut!

    I select the Place Section Callout tool and set the Drawing Seed to Struc - Framing Section, which is using "My Detailing Style", and place my section. It has the triangle on the wing terminator and is weight 2 and color 0 (black on my white background).

    To see what all the Properties in the detailing style are controlling look at this in the Help Contents:

     Help > Contents > MicroStation > Menus > Element Menu > Detailing Symbol Styles

    Hope this helps.



Children
  • Totally clear on that, thanks Paul.

    On the Annotate Tool Settings /Datagroup annotation section, I think it would be consistent with the library approach to have instant override of already-placed DG types...IMHO. Request material?  

  • On basic automation of DV annotation, this is what I understand of DATAGROUP ANNOTATION, I'm sure there is more to it so feedback on this is welcome!

    DRAWING RULES  AND DATAGROUP ANNOTATION CELLS

    Datagroup annotation rely on :

    - A set of annotation cells as models located in a file Annotation_DG.cel  , by default in the active dataset’s Cell folder. This file is controlled by the configuration variable BB_ANNOTATION_CELLLIB .

    - A ‘’Drawing Rules’’ interface

    1 – DG Annotation cells

    The cell management interface is accessed via the Manage Datagroup Annotation Cells tool. This tool automatically opens the Annotation_DG.cel file for editing/associating/creating, on completion of which closing the dialog will revert automatically to the previous dgn.

    Note that any edited models /new assignment to a type will need to be re-selected via the View Attributes/Building VIew/Architecture tab’s secondary dialog box before the changes are visible. I find this process has to take place in the Drawing Seed views before changes take effect.. Or perhaps restarting the application does it.. not too sure on this one.

    2 – Drawing Rules

    The Drawing Rules interface can be accessed from the View Attributes – Building – Architecture tab. Within this interface, the user can :

    - Associate an annotation cell from the Annotation_DG.cel list of cells with any Datagroup type.

    - Define offset values for the placement of the annotation cell when a DV is processed into a drawing

    - Select which Datagroup types are automatically annotated when a DV view is processed into a drawing

    DATAGROUP ANNOTATION SYMBOLOGY OVERRIDE

    The Annotate Tool Settings  functions as a symbology override interface and includes a section for Datagroup Annotation.

    The Datagroup section, when expanded, presents the complete list of DG items (same as in the Manage Datagroup Annotation Cells/Type dropdown list.) The right hand column displays the symbology and cell used for each DG item. These attributes can be selected and modified to suit.

    Note the override has no effect on already-placed DG annotation, which is something that should be improved IMO

    As an aside, the second section of the Annotate Tool Settings deals with the "manual" equivalent of Datagroup and Detailing Symbol automated annotation.

    The manual annotation tools rely on the Annotation.cel file,  which to be complete needs doors and windows models imported from BB_ANNOTATION.cel. Both  of those located by default in the active dataset’s cell folder – Annotation.cel configurable via TFANNOTATION_CELL_LIBFILE....