Early verbosity Setup

Using the other available methods to change the verbosity might be too late for the interesting part of your own application start-up. In this case you can use an environment variable to do some kind of early verbosity setup.

The environment variable CAPS_START_VERBOSITY can be used to overwrite the regular start-up verbosity level of LIBCAPS_VERBOSITY_DEFAULT. You can use the same verbosity words as defined in CAPS universe verbosity setup via INI File to define the start-up verbosity level.

For example:

CAPS_START_VERBOSITY=noisy caps-printing-coordinator

Verbosity Setup via INI

All executables related to the printing coordinator use a shared and an individual set of run-time INI files to support a generic way to configure their verbosity level.

By adding the following entry to a carefully selected INI file, you can limit the verbosity change to a specific component of the CAPS universe or set it for all components at once.

‍Examples: if you modify the caps.ini file, all CAPS universe components are affected. When modifying the capsdriver.ini file instead, only printer drivers are affected (but all at once), but not the printing coordinator itself.

The entry to add is the section [debug] and the keyword verbosity:

[debug]
verbosity=<level>

The supported level words are:

panic sets up LIBCAPS_PANIC
error sets up LIBCAPS_ERROR
warn sets up LIBCAPS_WARN
info sets up LIBCAPS_INFO
loud sets up LIBCAPS_LOUD
noisy sets up LIBCAPS_NOISY
debug sets up LIBCAPS_DEBUG

Note: The 'debug' verbosity word only works if debugging support was enabled at build-time.
If libcapsbase wasn't compiled with debugging support, no other component can make use of 'debug'. If libcapsbase was compiled with debugging support it depends on the other components (debugging support enabled or nor) if they make use of it.

Attention: Might interfere with CAPS universe early verbosity setup