Our 3D CAD supplier models have been moved to 3Dfindit.com, the new visual search engine for 3D CAD, CAE & BIM models.
You can log in there with your existing account of this site.
The content remains free of charge.
In this configuration file the basically structure of toolbars, menus and context menus is specified.
Note | |
---|---|
Normally you don't have to change these settings. The visibility of elements is controlled by menuvisibility_PARTdataManager.cfg. |
The block
Tweakmenu
contains
the specification of menu items and buttons without subitems[27]. This are most by far.
The menus are defined by three keys:
The internal name of a menu is stated in the key <name>MenuName.
Example by reference to Export menu:
ExportMenuName=ExportMenu
The title of a menu is stated in the key <name>MenuTitle.
Example by reference to Export menu:
ExportMenuTitle=&Export
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.
ExportMenuContent=ExportCadMenu,-,ExportFileMenuStatic,-,ExportNative,ExportMetafileBatch
Normally the key values don't have to be changed.
FileMenuName=FileMenu FileMenuTitle=&File FileMenuContent=FileOpen,FileSaveTemplate,-,actionRecentFilesList,-,FileExit
Individual customizing happens in the configuration file menuvisibility_PARTdataManager.cfg.
Normally the key values don't have to be changed.
ExportMenuName=ExportMenu ExportMenuTitle=&Export ExportMenuContent=ExportCadMenu,-,ExportFileMenuStatic,-,ExportNative,ExportMetafileBatch
Individual customizing happens in the configuration file menuvisibility_PARTdataManager.cfg.
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
Individual customizing happens in the configuration file menuvisibility_PARTdataManager.cfg.
Normally the key values don't have to be changed.
ViewMenuName=ViewMenu ViewMenuTitle=&View ViewMenuContent=View2D,ViewConnection,-,ViewThread,-,ViewConfigurator,ViewExplosion, ViewAssemblyStructure,AutomaticRecalc
Individual customizing happens in the configuration file menuvisibility_PARTdataManager.cfg.
Normally the key values don't have to be changed.
TableMenuName=TableMenu TableMenuTitle=&Tabelle TableMenuContent=TableShrink,TableUndoShrink,TableShowBmp,TableEdit
Individual customizing happens in the configuration file menuvisibility_PARTdataManager.cfg.
Normally the key values don't have to be changed.
ConfiguratorMenuName=ConfiguratorMenu ConfiguratorMenuTitle=&Konfigurator ConfiguratorMenuContent=ConfiguratorSave,ConfigratorSaveAs,-, ConfiguratorCreateTranslationFile,ConfiguratorShowConfig
Individual customizing happens in the configuration file menuvisibility_PARTdataManager.cfg.
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
Individual customizing happens in the configuration file menuvisibility_PARTdataManager.cfg.
Normally the key values don't have to be changed.
LayoutMenuName=LayoutMenu LayoutMenuTitle=&Window LayoutMenuContent=LayoutManagement,LayoutResetDefault
Individual customizing happens in the configuration file menuvisibility_PARTdataManager.cfg.
Normally the key values don't have to be changed.
HelpMenuName=HelpMenu HelpMenuTitle=Help HelpMenuContent=HelpHelp,HelpContextSensitive,HelpAbout,-,HelpLicenses,HelpPartInfo, HelpSysInfo
Individual customizing happens in the configuration file menuvisibility_PARTdataManager.cfg.
DebugMenuName=DebugMenu DebugMenuTitle=Debug DebugMenuContent=DebugShowMesh,DebugStartScript,DebugShowConfig,DebugShowMemory, DebugShowMemoryCheck,DebugVerboseAss,DebugFeedbackBuffer,DebugMakeSnapshot, DebugCompSnapshot,DebugInspectAddress
The values of the key menuOrder represent the desired sequence of the single menus.
menuOrder=FileMenu,ExportMenu,ErpMenu,ViewMenu,TableMenu,ConfiguratorMenu,ExtrasMenu, WindowMenu,HelpMenu,DebugMenu
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.
If a toolbar shall be shown in a new line, then include a line break “\n” in the list.
toolbarOrderTop=Details,Export,\n,SAP toolbarOrderLeft=Standard toolbarOrderRight=Assembly toolbarOrderBottom=ERP
Note | |
---|---|
If a
toolbar shall be hidden as a whole principally, this adjustment has to
be performed in the configuration file |
Toolbars are defined by three keys:
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
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
Normally the key values don't have to be changed.
ExportToolbar=MainWindow/Export ExportToolbarTitle=Export ExportToolbarContent=ExportCad,ExportFileMenu
Individual customizing happens in the configuration file menuvisibility_PARTdataManager.cfg.
Normally the key values don't have to be changed.
ViewsToolbar=MainWindow/Views ViewsToolbarTitle=Views ViewsToolbarContent=View2D,ViewConnection
Individual customizing happens in the configuration file menuvisibility_PARTdataManager.cfg.
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
Individual customizing happens in the configuration file menuvisibility_PARTdataManager.cfg.
Normally the key values don't have to be changed.
AssemblyToolbar=MainWindow/Assembly AssemblyToolbarTitle=Assembly AssemblyToolbarContent=ViewConfigurator,ViewExplosion,ViewAssemblyStructure, ExtrasAutomaticBuild,ViewCPMenu
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
Normally the key values don't have to be changed.
DetailsToolbar=MainWindow/Details DetailsToolbarTitle=Details DetailsToolbarContent=LevelOfDetailMenu
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.
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
Individual customizing happens in the configuration file menuvisibility_PARTdataManager.cfg.
Normally the key values don't have to be changed.
AddSapToolbar=MainWindow/Addsap AddSapToolbarTitle=Sap AddSapToolbarContent=sap
Individual customizing happens in the configuration file menuvisibility_PARTdataManager.cfg.
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
Individual customizing happens in the configuration file menuvisibility_PARTdataManager.cfg.
If you want to explicitly adjust the layout of the buttons, then set the value of “<name>ToolbarButtonStyle” on one of the following values:
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”.
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 | |
---|---|
Subitems can also be specified in the AltButtons block. |
Note | |
---|---|
More details can be found under menuvisibility_partdatamanager.cfg. |
The block [AltButtons] contains actions of the older class “AltButtons” (Connection point buttons for example). These actions serve as container for further actions.
Note | |
---|---|
Subitems can also be specified in the hasSubMenuActions block. |