Manual: document default value MsgFlags::IGNORE_NAME for registerFilter method

}

\end{minted}

\end{enumerate}

It should be noted that the \command{registerFilter} function by defaults adds the \parameter{IGNORE_NAME} message flag to receive all available messages if called without the message flag parameter:

\begin{minted}[frame=single,framesep=3pt,breaklines=true,tabsize=2,linenos]{c++}

messenger->registerFilter(this, &TestModule::filter);

\end{minted}

This means that a possibly set \parameter{input} parameter of the respective module has no effect.

If this behavior is undesired, the filter should be registered explicitly stating the desired message flags or \parameter{MsgFlags::NONE}.

The available message flags are described in detail in the following section.

\subsection{Message flags}

\label{sec:messageflags}

Flags can be added to the bind and listening methods which enable a particular behavior of the framework.

\begin{itemize}

    \item \textbf{REQUIRED}: Specifies that this message is required during the event processing.

    \item \parameter{REQUIRED}: Specifies that this message is required during the event processing.

    If this particular message is not received before it is time to execute the module's run function, the execution of the method is automatically skipped by the framework for the current event.

    This can be used to ignore modules which cannot perform any action without received messages, for example charge carrier propagation without any deposited charge carriers.

    \item \parameter{ALLOW_OVERWRITE}: By default an exception is automatically raised if a single bound message is overwritten (thus receiving it multiple times instead of once).