powered by CADENAS

Manual

Manual

1.7.9.2.2.1. menustructure_PARTdataManager.cfg

In this configuration file the basically structure of toolbars, menus and context menus is specified.

[Note] Note

Normally you don't have to change these settings.

The visibility of elements is controlled by menuvisibility_PARTdataManager.cfg.

1.7.9.2.2.1.1. Block [Tweakmenu]

The block Tweakmenu contains the specification of menu items and buttons without subitems[27]. This are most by far.

1.7.9.2.2.1.1.1. Menus

Menu specification

The menus are defined by three keys:

  • Internal name

    The internal name of a menu is stated in the key <name>MenuName.

    Example by reference to Export menu:

    ExportMenuName=ExportMenu

  • Display name of menus

    The title of a menu is stated in the key <name>MenuTitle.

    Example by reference to Export menu:

    ExportMenuTitle=&Export

    [Note] Note

    The key value of <name>MenuTitle (display name of the menu in the application) is translated in the file menustructure_<name of application>.def.

  • Specification of menu items which are basically available.

    The basically available actions (menu items) are stated in the key <name>MenuContent. The items are separated by comma.

    Example by reference to Export menu:

    ExportMenuContent=ExportCadMenu,ExportFileMenuStatic

    If you want to insert a separator in a menu, you have to insert a minus "-" in the list of actions at the desired position.

    Example:

    ExportMenuContent=ExportCadMenu,-,ExportFileMenuStatic,-,ExportNative,ExportMetafileBatch

    Example "Export" toolbar

    Example "Export" toolbar

Menus in detail

Example: All menus

Example: All menus

  • File menu

    Normally the key values don't have to be changed.

    FileMenuName=FileMenu
    FileMenuTitle=&File
    FileMenuContent=FileOpen,FileSaveTemplate,-,actionRecentFilesList,-,FileExit

    File menu

    File menu

    Individual customizing happens in the configuration file menuvisibility_PARTdataManager.cfg.

  • Export menu

    Normally the key values don't have to be changed.

    ExportMenuName=ExportMenu
    ExportMenuTitle=&Export
    ExportMenuContent=ExportCadMenu,-,ExportFileMenuStatic,-,ExportNative,ExportMetafileBatch

    Export menu

    Export menu

    Individual customizing happens in the configuration file menuvisibility_PARTdataManager.cfg.

  • ERP menu

    Normally the key values don't have to be changed.

    ErpMenuName=ErpMenu
    ErpMenuTitle=ERP
    ErpMenuContent=LinkDbLogin,LinkDbChangeGroup,CallLinkMgr,LinkDbBackToMgr,
     LinkDbCancelBackToMgr,LinkDbSendMail,LinkDbAddToDb,LinkDbClassify,LinkDbShowLegend,
     PreferredRanges,erp_psol_mm_vars,show_dbdata,SORTTABLE,erp_dbedit,DisplayMatButton,
     ChangeMatButton,SearchMatButton,erp_sap_showdis

    ERP menu

    ERP menu

    Individual customizing happens in the configuration file menuvisibility_PARTdataManager.cfg.

  • View menu

    Normally the key values don't have to be changed.

    ViewMenuName=ViewMenu
    ViewMenuTitle=&View
    ViewMenuContent=View2D,ViewConnection,-,ViewThread,-,ViewConfigurator,ViewExplosion,
     ViewAssemblyStructure,AutomaticRecalc

    View Menü

    View Menü

    Individual customizing happens in the configuration file menuvisibility_PARTdataManager.cfg.

  • Table menu

    Normally the key values don't have to be changed.

    TableMenuName=TableMenu
    TableMenuTitle=&Tabelle
    TableMenuContent=TableShrink,TableUndoShrink,TableShowBmp,TableEdit

    Table menu

    Table menu

    Individual customizing happens in the configuration file menuvisibility_PARTdataManager.cfg.

  • Configurator menu

    Normally the key values don't have to be changed.

    ConfiguratorMenuName=ConfiguratorMenu
    ConfiguratorMenuTitle=&Konfigurator
    ConfiguratorMenuContent=ConfiguratorSave,ConfigratorSaveAs,-,
     ConfiguratorCreateTranslationFile,ConfiguratorShowConfig

    Configurator menu

    Configurator menu

    Individual customizing happens in the configuration file menuvisibility_PARTdataManager.cfg.

  • Extras menu

    Normally the key values don't have to be changed.

    ExtrasMenuName=ExtrasMenu
    ExtrasMenuTitle=E&xtras
    ExtrasMenuContent=ExtrasWWWUpdate,ExtrasPARTadmin,ExtrasPARTbom,ExtrasBom,ExtrasVolumeCOG,
     Purchineering,Duplicates,Producibility,ExtrasServerJobList,-,ExtrasAutomaticBuild,-,
     ExtrasStartScript,-,ModePreferences,-,ShowPreferences

    Extras menu

    Extras menu

    Individual customizing happens in the configuration file menuvisibility_PARTdataManager.cfg.

  • Window menu

    Normally the key values don't have to be changed.

    LayoutMenuName=LayoutMenu
    LayoutMenuTitle=&Window
    LayoutMenuContent=LayoutManagement,LayoutResetDefault

    Window menu

    Window menu

    Individual customizing happens in the configuration file menuvisibility_PARTdataManager.cfg.

  • Help menu

    Normally the key values don't have to be changed.

    HelpMenuName=HelpMenu
    HelpMenuTitle=Help
    HelpMenuContent=HelpHelp,HelpContextSensitive,HelpAbout,-,HelpLicenses,HelpPartInfo,
     HelpSysInfo

    Help menu

    Help menu

    Individual customizing happens in the configuration file menuvisibility_PARTdataManager.cfg.

  • Debug menu

    [Note] Note

    Deactivated by default.

    DebugMenuName=DebugMenu
    DebugMenuTitle=Debug
    DebugMenuContent=DebugShowMesh,DebugStartScript,DebugShowConfig,DebugShowMemory,
     DebugShowMemoryCheck,DebugVerboseAss,DebugFeedbackBuffer,DebugMakeSnapshot,
     DebugCompSnapshot,DebugInspectAddress

Menu order

The values of the key menuOrder represent the desired sequence of the single menus.

Example for menu order

Example for menu order

Example:

menuOrder=FileMenu,ExportMenu,ErpMenu,ViewMenu,TableMenu,ConfiguratorMenu,ExtrasMenu,
 WindowMenu,HelpMenu,DebugMenu

[Note] Note

If a menu shall be hidden as a whole principally, this adjustment has to be performed in the configuration file menustructure_PARTdataManager.cfg.

1.7.9.2.2.1.1.2. Toolbars

Toolbar positions

The following keys represent the area of the toolbars in the window. The sequence of values (comma-separated) in each key represents the sequence of toolbars in the application.

  • toolbarOrderTop

  • toolbarOrderRight

  • toolbarOrderLeft

  • toolbarOrderBottom

If a toolbar shall be shown in a new line, then include a line break “\n” in the list.

Example:

toolbarOrderTop=Details,Export,\n,SAP
toolbarOrderLeft=Standard
toolbarOrderRight=Assembly
toolbarOrderBottom=ERP

This arrangement doesn't make sense but nicely illustrates the use.

This arrangement doesn't make sense but nicely illustrates the use.

[Note] Note

If a toolbar shall be hidden as a whole principally, this adjustment has to be performed in the configuration file menustructure_PARTdataManager.cfg.

Toolbar specification

Toolbars are defined by three keys:

  • Internal name

    The internal name of a toolbar is stated in the key <name>Toolbar. If you want to set a toolbar in an area of a main window, you must add "Mainwindow/" in front of the name of the toolbar.

    Example by reference to Export toolbar:

    ExportToolbar=MainWindow/Export

  • Display name of toolbars shown in their context menu (where you can enable/disable visibility)

    The title of the toolbar is stated by the key <name>ToolbarTitle.

    Example by reference to Export toolbar:

    ExportToolbarTitle=Export

  • Specification of toolbar buttons which are optionally available

    The optionally available actions (buttons) are stated in the key <name>ToolbarContent. The items are separated by comma.

    Example by reference to Export toolbar:

    ExportToolbarContent=ExportCad,ExportFileMenu

    Example "Export" toolbar

    Example "Export" toolbar

    If you want to insert a separator in a toolbar, you must insert a minus "-" in the list of actions at the position you want the separator to be displayed.

    LinkDbLogin,LinkDbChangeGroup,CallLinkMgr,LinkDbSendMail,LinkDbAddToDb,LinkDbClassify,
     LinkDbShowLegend,-,PreferredRanges

    Example "Export" toolbar

    Example "Export" toolbar

Toolbars in detail:

  • Export toolbar

    Normally the key values don't have to be changed.

    ExportToolbar=MainWindow/Export
    ExportToolbarTitle=Export
    ExportToolbarContent=ExportCad,ExportFileMenu

    Export toolbar

    Export toolbar

    Individual customizing happens in the configuration file menuvisibility_PARTdataManager.cfg.

  • Views toolbar

    Normally the key values don't have to be changed.

    ViewsToolbar=MainWindow/Views
    ViewsToolbarTitle=Views
    ViewsToolbarContent=View2D,ViewConnection

    Views toolbar

    Views toolbar

    Individual customizing happens in the configuration file menuvisibility_PARTdataManager.cfg.

  • Default toolbar

    Normally the key values don't have to be changed.

    StandardToolbar=MainWindow/Standard
    StandardToolbarTitle=Standard
    StandardToolbarContent=TableShowBmp,ExtrasPARTbom,-,AutomaticRecalc,-,ExtrasWWWUpdate,
     HelpSysInfo,Export_PDFDATASHEET,-,ShowEolLines,BugreportStatus,din962,prefcatalogs,
     StartupPageClicked,PortalToolbarClicked,StorageButtonClicked
    

    Default toolbar

    Default toolbar

    Individual customizing happens in the configuration file menuvisibility_PARTdataManager.cfg.

  • Assembly toolbar

    Normally the key values don't have to be changed.

    AssemblyToolbar=MainWindow/Assembly
    AssemblyToolbarTitle=Assembly
    AssemblyToolbarContent=ViewConfigurator,ViewExplosion,ViewAssemblyStructure,
     ExtrasAutomaticBuild,ViewCPMenu
    

    Assembly toolbar

    Assembly toolbar

    Individual customizing happens in the configuration file menuvisibility_PARTdataManager.cfg.

    In order to control the submenu buttons of "Connection Point" the block [ALTBUTTONS] is used:

    [ALTBUTTONS]
    ViewCPMenuName=ViewCPMenu
    ViewCPMenuContent=ViewCP,ViewCPNot,ViewCPMarked

  • Details toolbar

    Normally the key values don't have to be changed.

    DetailsToolbar=MainWindow/Details
    DetailsToolbarTitle=Details
    DetailsToolbarContent=LevelOfDetailMenu

    Details toolbar

    Details toolbar

    The main button is set in the block [Tweakmenu] by default.

    [Tweakmenu]
    DetailsToolbarContent=LevelOfDetailMenu

    The sub-buttons are set in the block [ALTBUTTONS]:

    [ALTBUTTONS]
    LevelOfDetailMenuName=LevelOfDetailMenu
    LevelOfDetailMenuContent=HI,MED,LO

    Individual customizing happens in the configuration file menuvisibility_PARTdataManager.cfg.

  • Link database toolbar

    Normally the key values don't have to be changed.

    LinkDatabaseToolbar=MainWindow/LinkDatabase
    LinkDataBaseToolbarTitle=Link database
    LinkDatabaseToolbarContent=LinkDbLogin,LinkDbChangeGroup,CallLinkMgr,LinkDbSendMail,
     LinkDbAddToDb,LinkDbClassify,LinkDbShowLegend,-,PreferredRanges,erp_psol_mm_vars,
     show_dbdata,SORTTABLE,erp_dbedit,DisplayMatButton,ChangeMatButton,SearchMatButton,
     -,erp_sap_showdis

    Link database toolbar

    Link database toolbar

    Individual customizing happens in the configuration file menuvisibility_PARTdataManager.cfg.

  • Sap toolbar

    Normally the key values don't have to be changed.

    AddSapToolbar=MainWindow/Addsap
    AddSapToolbarTitle=Sap
    AddSapToolbarContent=sap

    Sap toolbar

    Sap toolbar

    Individual customizing happens in the configuration file menuvisibility_PARTdataManager.cfg.

  • Classification toolbar

    Normally the key values don't have to be changed.

    ClassificationToolbar=MainWindow/Classification
    ClassificationToolbarTitle=Classification
    ClassificationToolbarContent=ct_add_class,ct_delete_class,ct_edit_class,ct_move_class,
     ct_add_datasets,ct_delete_datasets,ct_edit_dataset,ct_move_datasets,ct_copy_dataset,
     ct_edit_views,ct_batch_update,ct_move_geomsearch,ct_update_tool,ct_create_classification

    Classification toolbar

    Classification toolbar

    Individual customizing happens in the configuration file menuvisibility_PARTdataManager.cfg.

Button layout

If you want to explicitly adjust the layout of the buttons, then set the value of “<name>ToolbarButtonStyle” on one of the following values:

Value Meaning
IconOnly / no entry Only display the icons of the buttons.
TextOnly Only display the text of the buttons.
TextBesideIcon The text appears beside the button icon.
TextUnderIcon The text appears under the button icon.

Examples by reference to "Standard" toolbar

  • StandardToolbarButtonStyle=IconOnly

    IconOnly exemplified by Standard toolbar

    IconOnly exemplified by Standard toolbar

    [Note] Note

    Text is displayed in the tooltip.

  • StandardToolbarButtonStyle=TextOnly

    TextOnly exemplified by Standard toolbar

    TextOnly exemplified by Standard toolbar

  • StandardToolbarButtonStyle=TextBesideIcon

    TextBesideIcon exemplified by Standard toolbar

    TextBesideIcon exemplified by Standard toolbar

  • StandardToolbarButtonStyle=TextUnderIcon

    TextUnderIcon exemplified by Standard toolbar

    TextUnderIcon exemplified by Standard toolbar

1.7.9.2.2.1.1.3. Context menus

All context menu commands are listed comma-separated under block Tweakmenu -> key IndexTreePopupMenuContent.

Detailed figures can be found under Section 1.7.9.2.2.2.2.2, “PARTdataManager: Action names of context menu commands”.

1.7.9.2.2.1.2.  Block [hasSubMenuActions]

The block [hasSubMenuActions] contains the standard declaration for all actions with an additional menu level (for example Recent parts or Purchineering). The name of the top level action is set as key. Actions of the next deeper level are listed comma separated.

[Note] Note

Subitems can also be specified in the AltButtons block.

Example 1:

Declaration in config

Declaration in config

Display in UI: "Recent parts" menu item

Display in UI: "Recent parts" menu item

Example 2:

Declaration in config

Declaration in config

Display in UI "Purchineering" menu item, which has further submenus

Display in UI "Purchineering" menu item, which has further submenus

[Note] Note

More details can be found under menuvisibility_partdatamanager.cfg.

1.7.9.2.2.1.3.  Block [AltButtons]

The block [AltButtons] contains actions of the older class “AltButtons” (Connection point buttons for example). These actions serve as container for further actions.

[Note] Note

Subitems can also be specified in the hasSubMenuActions block.

Example:

Declaration in config

Declaration in config

Display in UI

Display in UI



[27] Subitems are specified by the classes "hasSubMenuActions" and "AltButtons".