Panel: Logging¶

Description¶

Chartist has a built-in logging module (disabled by default). If an unknown error occurs and can be reproduced, use the logging module to determine where the problem is.

Important

Using logging can severely degrade performance, especially when using Blender’s built-in console (Windows only). Leave all logging options disabled for optimal performance.

../_images/ch_panel_logging.png — The Logging Panel.¶

Panel Components¶

Button: Toggle System Console¶

Toggles the Blender System Console window where information is printed. To launch from terminal (macOS and Linux) See here.

Button: Classes¶

Toggles python Class information. Developer level.

Button: Functions¶

Toggles python function information. Developer level.

Button: Time¶

Toggles the operator (class) takes to completion. User level.

Button: Info¶

Toggles general information. User level.

Button: Debug¶

Toggles debug information. User level. Verbose

Usage Examples¶

Use the Logging Module¶

Click on Toggle System Console
Check the relevant checboxes on level of information you want to receive.
Do something within the Chartist extension.
Information on the current running task will be printed to the console.

../_images/ch_help_logging_use.png — The Logging module in use.¶

Launch Blender from Terminal¶

The Blender Windows build includes a console where logging is printed to. For Linux and macOS, Blender needs to be launched from the terminal to enable logging.

To launch Blender from terminal:

macOS
- Open Terminal.
- Run Blender’s binary inside the .app bundle (adjust path if saved elsewhere):
```
/Applications/Blender.app/Contents/MacOS/Blender
```

Linux
- Open Terminal.
- Run Blender directly from its installed path (or custom location):
- Edit the version to match, below is for Blender 5.0.1.
```
/home/username/Applications/blender-5.0.1/blender
```