Preferences
To configure preferences in the Preferences dialog, select Edit>Preferences or Window>Preferences>S32 Configuration Tools in S32 Design Studio from the Menu bar.
Note: You can restore settings to default by selecting Restore
Defaults in the lower right corner of the dialog.
Several settings are available.| Item | Description |
|---|---|
| Line ending style | Select between Windows (CR + LF), Linux (LF), or Default (based on host). |
| Generate files read-only | Prevent modifying the source files unintentionally. Generated source files are marked as read-only. |
| Generate source folder | At build time, automatically create a folder including source files. |
| Create empty configuration if no yaml is available | Generates a configuration even if no yaml is present. |
| Always overwrite files without asking | Update existing files automatically, without prompting. |
| Always show details before Update Code | Review changes before the project is updated. |
| Undo history size | Enter the maximum number of steps that can be undone. Enter 0 to disable. |
| Show pin label & identifier table columns (Pins tool) | Select to show the pin label and the label identifier in the relevant views. |
| Require Identifier for Pins (Pins Tool) | Controls generation of pins “Identifier” related warnings. With this preference enabled, warnings will be generated for bidirectional signals that have no Identifier set. |
| Show Overview window on opening configuration for the first time | Open the Overview dialog on opening configuration for the first time. |
| Automatically load last configuration on startup | Avoid the startup window and load the last used configuration instead. |
| Enable Code Preview | Controls how the code is generated. When this preference is enabled, code
generation is performed automatically after every change in the configuration and
the Code Preview is updated accordingly. When this preference is disabled, code
generation is stopped, warning message is displayed in Code Preview window, and the
action can be manually triggered by using one of the available options:
|
| Component template folder | The path to the folder with component templates. Keep empty to use the default path. The default path is to folder component_templates in data of the Config tools. |
| Allow component migrations | When a configuration associated with a toolchain project is open, the peripheral tool automatically checks if the configuration components match the project and suggests a migration if they are not. |
| Enable animations | Enables animations in the user interface, such as smoother scrolling or opening a drop-down menu. |