PNI

Configurations

Object Editors

Adding Back Specials Pulldown

PNI removes the "Specials" pulldown from some of the object editors (like Pole). The simplest way of adding the "Specials" pulldown back is to create a customisation product and adding the the files named (with the path) "pni_editors_config\resources\base\data\pole_editor_config.xml" and "pni_editors_config\resources\base\data\pole_editor_gui.xml". The information in each file should look like the following…

+ show block

Config File:

<?xml version="1.0" encoding="ISO-8859-1" standalone="yes"?>
<config base="pni_object_editor.pni_structure_editor_config.xml">
    <plugins>
        <plugin name="transactions" class_name="pni_modelit_pole_editor_plugin"/>
        <plugin name="editor_pole" class_name="pni_pole_editor_plugin"/>
    <plugin name="rwo_specials" class_name="rwo_specials_plugin"/>
    </plugins>
</config>

GUI File:

<?xml version="1.0" encoding="ISO-8859-1" standalone="yes"?>
<gui base="pni_object_editor.pni_structure_editor_gui.xml">
    <toolbar name="annotate">
             <pulldown mode="simple" caption="annotate" style="text">
                <action name="editor_annotation.set_annotation"/>
            <section/>
            <action name="editor_pole.place_bond_anno"/>
            <action name="editor_pole.place_dc_anno"/>
            <action name="editor_mit_presentation.place_connectivity_diagram"/>
            <section/>
            <action name="editor_mark_as_correction.mark_as_correction"/>
            <action name="editor_mark_as_correction.unmark_as_correction"/>
        </pulldown>
    </toolbar>
  <toolbar name="custom" >
    <pulldown mode="simple" caption="specials" role="rwo_specials" >
    </pulldown>
  </toolbar>
    <dock name="top">
        <toolbar name="lock"/>
        <toolbar name="transaction"/>
        <toolbar name="form"/>
        <toolbar name="goto_context"/>
        <section/>
        <toolbar name="other"/>
        <toolbar name="annotate"/>
        <toolbar name="associate"/>
        <toolbar name="tools"/>
        <toolbar name="custom"/>
        <toolbar name="help"/>
    </dock>

    <work_area>
        <paned_window side_by_side="no" dynamic="no">
            <self stretch="0"/>
            <tab_box>
                <plugin plugin_name="field_lister" stretch="100"/>
                <plugin plugin_name="editor_related_items"/>
            </tab_box>
        </paned_window>
    </work_area>
</gui>

User Objects

Adding User Objects to History

• Your new object exemplar must be inherit from planning_status_mixin.
• create an entry like swg_dsn_admin_engine.define_table_code(5407301,:your_object)
• create entry in mit_manager
  • mit_manager.table_name_to_code[:your_object] « 540731
  • mit_manager.code_to_table_name[5407301] « :your_object

Below is the path to the components information.

+ show block

!traceback!(a sw:terminal, 15)
condition(information).raise(:unknown_pni_table_code, {:table_name, (ds)"Future Splice Point"})
user!future_sp_pt1003:(3731487).derive_info()
user!future_sp_pt1003:(3731487).pp_is_data_correction_in_design?()
a pni_job_component_framework(job_component_gui).is_data_correction_in_design?(user!future_sp_pt1003:(3731487))
      sw:simple_vector:[1-11].fast_keys_and_elements()
    sw:set(1).valid_indices(False)
  sw:set(1).fast_elements()
a pni_job_component_framework(job_component_gui).get_object_trees_for_collection(sw:set(1))
a pni_job_component_framework(job_component_gui).perform_with_vector(:|get_object_trees_for_collection()|, sw:simple_vector:[1-1])

Enabling Geometry Actions

The user records need to have the following methods/constants available for the Highlight, Goto, Select, and Place One buttons to work properly. It is up to you how to determine the geometry field to use if your object has multiple objects.

• safe_primary_geometry - This returns the geometry field name as a symbol
• get_spatial_context_names() - This returns all possible geometry field names you want to interact with the application
• primary_spatial_context_name - For "go to" functionality in PNI. Returns the geometry name to use.
• get_spatial_context() - For "go to" functionality in PNI. Returns spatial_context for the object. (see code below)
• default_geom_field_name - For "place" action to be available

+ show block

# method looks similar to:
_method rec_exemplar.get_spatial_context()

    _local target_world << _self.source_view.world(0,0)
    _local ace_name
    _local geom_set << geometry_set.new()

    _for ag _over _self.geometry_set_for_world( target_world ).fast_elements() 
    _loop
        geom_set.add( ag )
    _endloop    

    context_name << _self.spatial_context_name

    sc << spatial_context.new( context_name, _self )

    sc.add_element( target_world, geom_set, _unset, ace_name )

    _return sc
_endmethod

3rd Party Products