Customizing the Part Editor - Intergraph Smart 3D - Reference Data - Hexagon

Intergraph Smart 3D Structural Manufacturing Reference Data

Language
English
Product
Intergraph Smart 3D
Subproduct
Structural Manufacturing
Search by Category
Reference Data
Smart 3D Version
13.1

The Part Editor configuration file is named SMS_Viewer.xml. All the property definitions are referenced through the SMS_PROPERTIES.xml file using the key-word node name <INCLUDE_PROPERTY> or <INCLUDE_GROUP>.

The configuration file is created and stored in the [Reference Data Folder]\SharedContent\StructManufacturing\SMS_SCHEMA\ folder.

If the Part Editor is unable to locate the configuration file, the Attribute Editor runs in read-only mode.

Basic XML Structure

The root node of the configuration file is <PART_EDITOR_CONTROL>. At the highest level, the configuration file is divided into the following categories:

  • <VALIDATION_CONTROL> - Contains the settings for the validation engine. This category also determines the kinds of validation that are run when a part is persisted and the level of error that halts persistence for each type.

  • <ATTRIBUTE_EDITOR_CONTROL> - Contains the settings for controlling the behavior of the Attribute Editor, for determining how attributes are validated, and for controlling what attributes are included for general part attribute sets, marking attribute sets, and contour attribute sets.

    The property definitions are not found in the SMS_VIEWER.xml file. They are referenced from the SMS_PROPERTIES.xml file. The property definitions in the SMS_PROPERTIES.xml file are also reused in the SMS_ANNOTATION.xml file. Because of this, changes made in the SMS_PROPERTIES.xml file should be made with caution as they can have consequences in both the SMS_VIEWER.xml file and the SMS_ANNOTATION.xml file.

  • <PREDEFINED_BEVEL_GRIND_CONTROL> - Contains the settings for predefined bevels and grinds and their behavior within the attribute editor.

OUTPUT_ANNOTATION

The <OUTPUT_ANNOTATION> node contains the settings for the text arguments and geometry arguments used to construct the annotation object.

Each annotation type XML node looks similar to the following figure:

Annotation XML Example

  • The first node in the SMS_OUTPUT_ANNOTATION is SMS_PLACEMENT. This node acts as a container for the INCLUDE_CONDITION nodes. These nodes are referenced through the INCLUDE_CONDITION node.

  • The definitions of <CONDITION> are defined in <ANNOTATION_ATTRIBUTE_CONTROL>/<PLACEMENTENT_CONDITIONS>/<CONDITION>. The following example shows several <CONDITION> definitions for the local and global axis control, at 45 degree increments.

    CONDITION Example

  • The AXIS="Local" parameter uses the coordinate system defined by the object against which the annotation is being placed to define the orientation and rotation of the annotation object. Each annotation is rotated according to the specified angle in relation to the curve.

    Annotation Rotation Example

  • The AXIS="Global" parameter uses the drawings coordinate system to define the orientation and rotation of the annotation object. Each annotation is always rotated according to the specified angle regardless of the geometry it is placed on or where it is placed in the drawing.

    Annotation Rotation Example - Global

SMS_INPUT_ARGS

This group contains two sets of nodes that are important to the annotation functionality: <SMS_TEXT_ARGS> and <SMS_GEOM_ARGS>.

  • The <SMS_TEXT_ARGS> node defines the text properties of the annotation and system-level parameters that are unavailable to the user, such as GEOM2D_GUID.

    These are all system-level parameters. They reference the SMS_PROPERTIES.xml file through a reference key-word of either <INCLUDE_PROPERTY> or <INCLUDE_GROUP>. In the case of INCLUDE_GROUP, it is referencing a node collection <ANNOTATION_ATTRIBUTE_CONTROL>/<ATTRIBUTE_GROUPS>/<ATTRIBUTE_GROUP> where the purpose is specified by the system depending on which type of part is being worked with at the time. In this way, the <INCLUDE_PROPERTY> can be added conditionally for profiles but not for plates.

    If you want to provide different default values for a given annotations type, you can specify a new value here and the software uses it as the default and over-writes any defaults that are defined in the SMS_PROPERTIES.xml file. In the following example, the VALUE, READONLY, UNIT, and UNIT_TYPE attributes of the property are over-ridden.

    SMS_TEXT_ARGS Example

    Additional optional attributes that you can use are:

    SOURCE - Defines how an annotation property is inherited from the currently selected object. If you create a new annotation, and the property that annotation should inherit from is ambiguous, this attribute is used.

    DISPLAY_UNIT - An alternative display unit override. Normally the system displays units defined by the Units of Measure Service, which you set by using the S3D Options dialog box from the 3D View menu. However, if you specify DISPLAY_UNIT, the unit is converted into this unit for display in the various grid views.

    DISPLAY_PRECISION - An alternative display precision. Normally, the system displays two digits past the decimal point for a given numerical value. The value that is stored on the object is rounded to fit this requirement for display purposes. The values on the objects are stored with full precision; they are only rounded for display. However, if you specify DISPLAY_PRECISION, then the value is rounded with this many significant figures past the decimal point.

    SHEET_UNIT - An alternative display unit override that overrides DISPLAY_UNIT when the values are converted for display in the Part Monitor sheet header. If DISPLAY_UNIT is not specified, then SHEET_UNIT overrides the display units for the sheet header to the specified unit. All other grid views still display the system defined units.

    SHEET_PRECISION - An alternative display precision that overrides DISPLAY_PRECISION when the values are for display in the Part Monitor sheet header. If DISPLAY_PRECISION is not specified, then SHEET_PRECISION overrides the precision for the sheet header of the values. All other grid views still display the default two units of precision.

    DISPLAY_UNIT, DISPLY_PRECISION, SHEET_UNIT, and SHEET_PRECISION can also be specified in the SMS_PROPERTIES.xml file so that that they apply to all instances where the property definition is used.

  • The <SMS_GEOM_ARGS> node defines the geometry properties of the annotation, such as text offset and linear and angular dimensions and relationships. This determines how the annotation is drawn.

  • TextSize determines the default size and scale of the annotation. You can change this value in the Annotation Editor by increasing or decreasing the text size for a given annotation entity, but this is where the default value is determined for a given annotation type.

  • Both of the SMS_INPUT_ARG Property node groups are used by, and highly integrated with, the Annotation Symbols rules.