This allows for the definition of additional user packages that should be available in MeVisLab.

This attribute has two subattributes: pathRoot and path. pathRoot specifies a root path to which all subsequent path entries are relative. path should typically consist of a pair of package group and package, separated by a slash.

Example:

                
    PackagePaths {
      pathRoot = "C:/Users/a_user/Documents/Packages"
      path     = MyPackageGroup/MyPackage

      pathRoot = "C:/Users/a_user/Documents/Development/MeVisLab"
      path     = MyOrganization/Package1
      path     = MyOrganization/Package2
    }   
              

Writes all console output to the specified file. You can use $(LOCAL) to reference files relative to the settings file.

Shows module panels when the network is loaded. It is also available from the Preferences dialog.

Automatically reloads the MDL/script files of a module when a module panel is opened (recommended for fast prototyping; no explicit module "reload" is required). It is also available from Preferences dialog.

Automatically saves networks when changed. It is also available from Preferences dialog.

Prints messages when entering and leaving command-handling scripting functions.

By default, deprecated modules (or modules in other hidden module groups) do not appear in the module search. If this option is set, modules by the current user will always be shown.

	Note
	The author name for a module must be exactly the same as the username in the Preferences dialog.

Overrides the location of the MeVisLab documentation, giving the base path as a URL. A suitable default is, e.g.: https://www.mevislab.de/docs/current.

MeVisLab has an integrated spell checker (based on Hunspell) for English text in the module help editor. With this option, users can include an extra dictionary file.

With this option, modules can be loaded at startup of the IDE (created in an invisible network), which can in turn execute code and, for example, initialize preference variables. This tag can be specified multiple times.

The MeVisLab debug console, by default, refreshes immediately after each output to remain up-to-date (for example, in the case of crashes). However, this can lead to problems with event handling and may slow down performance. Disable immediate refreshes by setting to YES; then the console is only updated when MeVisLab is idle or processes events for other reasons.

Windows only.

Sets additional directories from which to load DLLs. Multiple paths can be specified, separated by “;”; this entry can also be provided more than once.

It is also possible to reference environment variables in a path with ${}, e.g., ${CUDA_PATH_V11_4}, or even ${PATH}.

Sets the cache size for the ML image processing (in MB). It is also available from Preferences dialog.

Allows the specification of a directory that can contain alternative mouse cursors to be used in Inventor scenes. See the comments in $(MLAB_ROOT)/MeVis/Foundation/Sources/MLInventorGUIBinding/SoQtViewerProxy.h.

Use Qt for rendering fonts in SoView2D and similar viewers if set to YES (default). Otherwise, it uses a simpler font rendering engine that lacks Unicode support.

Sets the font to use for font rendering.

Same as above, but only affects the simpler, not Qt-based font rendering.

Scales all MDL panels with this factor. Default is 1.

Defines the QML style to be used in the QuickView control.

If set to YES, MeVisLab will not look for updated MDL/script files after the initial load. It is used for application deployment (defaults to YES for applications and NO for IDE).

Runs MeVisLab with a low process priority.

Sets the color with which text is drawn on the splash screen. It must be a 6-digit hex value (without '#').

Hides initialization messages on the splash screen.

If set to NO, it disables Python multi-threading support. Disable this in case of issues.

Sets the maximum number of threads to be used by the ML image processing pipeline for standard image processing. The default is the number of virtual cores in the system.

Sets the maximum number of threads to use by the GVR framework. The default is the number of virtual cores in the system. It is also available from Preferences dialog.

If enabled, time stamps in the log will be printed with a higher precision (the actual precision depends on the system). This can be useful if the exact timing of events is important.

If this option is ON, .mlab files will not store the position and state of module panels if they are closed at the time of saving. This can reduce the changes displayed in DIFF tools when using a version control system.

If set to ON, it fixes flickering of fullscreen panels with OpenGL content (for some setups).

If set to NO, Debug mode tools (according to the debug suffix of the executable name) will be called from MeVisLab if MeVisLab is in Debug mode. Otherwise, the faster release mode variant will always be preferred. The default is YES.

Sets whether to store the module cache files in a directory outside the installation directory. Default is NO.

If this option is set, pop-up menus do not show icons for their entries (on some platforms this is a no-op, as there are no icons shown anyway).

If this option is set, MeVisLab (and applications based on MeVisLab) will not display a warning if the current license is about to expire.