| genre | Inspectors |
| status | stable |
| author | Wolf Spindler |
| package | MeVisLab/Standard |
| dll | MLDiagnosis |
| definition | mlDiagnosis.def |
| see also | CoreControl, ModuleView, RuntimeView, CacheView, Checksum, Info, Console |
| keywords | diagnosis, debugging, messages, log, file, outputting, outstream, information |
The module MLLogFile redirects all selected ML messages into a user defined file.
The types of messages that are printed into that file can be selected by a simple filter.
There is a similar module Console that writes the information into a console.
| Cerrs: Bool | File Name (logFile): String | Message Type: Bool |
| Clear: Trigger | Full File Name: String | Messages: Bool |
| Couts: Bool | Function Name: Bool | Other: Bool |
| Debug Infos: Bool | Handling: Bool | Time: Bool |
| Enable: Bool | Information: Bool | Warnings: Bool |
| Errors: Bool | Library Prefix: Bool | |
| Fatal Errors: Bool | Line Number: Bool | |
| File Name (logFileName): Bool | Log File State: String |
If checked, information messages are being written into the log file.
If checked, warning messages are being written into the log file.
If checked, error messages are being written into the log file.
If checked, fatal error messages are being written into the log file.
If checked, debug information messages are being written into the log file.
If checked, std::cout messages are being written into the log file.
If checked, std::err messages are being written into the log file.
If checked, other messages are being written into the log file.
If checked, the line number of where the message was generated is written into the log file.
If checked, the name of the file where the message was generated is written into the log file.
If checked, the time stamp of when the message was generated is written into the log file.
If checked, the function name of where the message was generated is written into the log file.
If checked, the message's content is being written into the log file.
If checked, the message's handle is being written into the log file.
If checked, the prefix of library in which the message was generated is written into the log file.
If checked, the message's type is being written into the log file.
If checked, the logging of messages is activate.
Sets path and file name of the log file (with variables).