The tuchulcha options are stored using the QSettings mechanism.

On Windows systems, this causes the settings to be stored in the Windows registry. On Unix systems, settings are stored in the users .config directory.

General Configuration

options config page

Startup and Workflow Execution

The first option causes an Updating Plugin Metadata run at each start of tuchulcha. This makes sure that the latest plugin information is available before loading any workflow file.

This option is useful if plugins are added/changed frequently. If this is not the case, deactivating this option may save some time at startup.

The second option causes a message box to show up after creation of the background process used on Interaction with Charon-Suite Plugins but before this process is started. This is the right moment to attach a debugger, e.g. to catch exception messages or failing assertions. This may be neccessary if the crash message does not provide eanough information or if you want to trace plugin functions during execution.

Plugin Config

Switch between debug and release configuration of the plugins.

When compiling a plugin in debug mode, it is recommended to append a _d postfix to the generated shared library file. Using CMake, this is done by setting CMAKE_DEBUG_POSTFIX to _d. This way it is possible to have both configurations of a plugin in the same directory.

If both variants exist, this switch controls which one is used. When the Debug variant is selected, the unsuffixed library name is used as fallback.

Warning: If only the debug variant (with _d postfix) is available but the release configuration is selected, the plugin won't be found.

Plugin Version Check

On plugin load, the version of charon-core used to compile the plugin and used by tuchulcha may be compared.

Here it is possible to change the behavior of handling plugins with a version mismatch. It is also possible to disable this check completely.

Possible values:

disable version check
print warning if check failed, plugin will be used nevertheless
discard failing plugins, version mismatch is treated as error

See Also: Version Check

Paths Settings

options paths page

This section serves to configure the paths where the plugin library files are located. In each of the three input lines it is possible to enter a list of paths, separated by semicolon.

When running in debug config, the full search paths is assembled by appending the global and debug plugin paths. In release config, the global and release plugin paths are used. The plugin mode may be changed in Plugin Config.

So the first line should contain paths that should be searched independend of the selected configuration. This may be e.g. the path of the precompiled plugins shipped from the charon-suite website. The second line may contain the release output path(s) of your self-compiled plugin project(s) and the third line the debug output path(s) of the same project(s).

Per default, only the global path is set to the directory of the shipped charon-suite plugins (in /usr/lib/charon-plugins at unix systems and beside the tuchulcha executable on windows systems).

Exclude List

options excludes page

Here you may enter a list of library names which should not be treated as charon-suite plugins. Files matching the wildcard expressions (may contain "*") are skipped during the metadata update. This way, it is possible to avoid the "no plugin" lines in the update summary.

Appearance Settings

options appearance page

To change the appearance of the main toolbar in the tuchulcha window, it is possible to select between text and icon and combined ways to display the tool buttons.