Edit Settings

Table of Contents

• UaModeler
  • Automatic Check for Updates
• Code Generation
  • General
  • Author Information
• Modeling
  • Edit NodeIds
  • Editing of NodeAccessInfo
  • Editing of User Defined Extensions
  • Information Model Documentation
  • Multiple Namespace Support

To edit the following settings, choose Settings → Edit Settings from the menu bar. The settings are split into three groups: UaModeler, Code Generation, and Modeling.

UaModeler

Automatic Check for Updates

If Check for Updates is enabled, UaModeler regularly checks whether an update is available. You can specify the Update Interval in days using the respective input field. If this value is set to 0, UaModeler checks for updates on every start-up.

Automatic Check for Updates

To manually check for updates, choose Help → Check for Updates… from the menu.

Code Generation

General

If Generate Date is checked, the current date will be written into the headers of the generated files (see screenshot).

To prevent that generated files are accidentially overwritten, a dialog window appears if a file to be generated already exists. You can change this default behavior. There are four options:

Ask for overwriting

This is the default behavior. You will be asked for every file whether it should be overwritten.

Overwrite all

When regenerating code, all files are overwritten, except implementation files, i.e. the files where own code is added.

Overwrite all including implementation files

In this case all files, including the files for adding own code are overwritten.

Overwrite none

UaModeler leaves all existing files untouched.

If Overwrite all or Overwrite none is selected, the files which would replace existing files are written to a temporary directory. If you would like to manually overwrite some or all of these files, choose Project → Overwrite generated files manually from the menu bar. A dialog window will open (see screenshot) where it is possible to select the files to overwrite.

Manually overwrite files

Author Information

In the Author section of the dialog you can add some infomation about the author. This data will be written into the headers of the generated files:

Author and Date in Generated Files

Note

Author Information is saved in UaModeler’s application settings and not in the Project settings.

Modeling

Edit NodeIds

By default, the user cannot edit the NodeIds of UaNodes in custom models: The UaModeler sets the NodeIds and takes care that they are unique. You can enable the editing of the NodeIds by checking the box “Enable editing of NodeIds”. For types, the NodeIds have to be numeric, for instances, all kinds of NodeIds are allowed. If you choose to edit the NodeIds by hand, the UaModeler will still check if they are unique.

Note

Not all kinds of NodeIds are supported by each of the templates. The Ansi C Templates only support numeric and string NodeIds. The C++ and .NET templates only support numeric NodeIds.

Editing of NodeAccessInfo

These settings can be used to control the behavior of the NodeAccessInfo extension.

NodeAccessInfo is disabled by default. Check the box NodeAccessInfo enabled to enable it. It will then show up in the Extensions View.

The drop-down menu Mode allows you to select the mode to use for NodeAccessInfo. See Enabling NodeAccessInfo for more information.

If Add Default Roles is checked, a set of default roles/groups to be used for NodeAccessInfo is enabled (see Adding Users and Groups).

Settings for NodeAccessInfo

Editing of User Defined Extensions

User Defined Extensions are disabled by default. Check the box User defined extensions enabled to enable them. UaModeler’s XML editor to display and edit user defined extensions will then show up in the Extensions View.

The input field Default Extension Namespace URI can be used to define the namespace to use for user defined extensions (see User Defined Extensions). Leave the field empty to disable this feature.

Settings for User Defined Extensions

Information Model Documentation

The editor for Node Documentation is disabled by default. You can enable it by checking Documentation enabled.

The box Markdown enabled is checked by default. It can be disabled to enter Markdown-like text that should not be interpreted as Markdown code.

By checking Disable Code Generation you can specify whether the documentation entered in the extensions editor should be included in generated code. Generic documentation is included nevertheless and cannot be disabled.

Settings for Information Model Documentation

Multiple Namespace Support

If Support multiple namespaces in one XML file is checked, such XML files can be added using the “Add Existing Model” dialog. It is not possible to use them for updating a model from a file.