logs issues within the system More...

#include <issuelogger.h>

Public Types
enum	LogMessageFormat { lmFULL, lmREGULAR, lmCODE }

enum	IssueType { itNone =0, itCritical =1, itError =2, itWarning =4, itMessage =8, itDebug =16, itAll =255 }
	identifies the severity of the issue More...

Public Member Functions
	IssueObject (const QString &message, int it, quint64 id)

QString	message () const

QDateTime	time () const

int	type () const

QString	logMessage (LogMessageFormat lmf=lmFULL) const

void	addCodeInfo (int line, const QString &func, const QString &file)

quint64	id () const

int	codeLine () const

QString	codeFunc () const

QString	codeFile () const

void	stream (std::ofstream &stream, LogMessageFormat frmt)

Detailed Description

logs issues within the system

Ilwis error/warning system is a system that stacks issues that arose in a logger in the kernel. Usualy methods that generate an error also give a false/invalid return value. It is up to the programmer than to decide what to do. He always has a trace of what happened in the issue logger. With creation of objects the issues that arose during creation are transfered to the objects after creation while the general stack is cleared. The philosophy of the error system is that it stays out of the way unless the client wants is.

Member Enumeration Documentation

enum Ilwis::IssueObject::IssueType

identifies the severity of the issue

Critical errors will stop the system. Usualy are errors in the configuration of the system Errors will not stop the system but probably will abort the action or miss some part of the action Warnings are meant to signify non critical changes to the action. Results might be sligthly off but not overly so Messages are just messages, no effect on the action

The documentation for this class was generated from the following files:

issuelogger.h
issuelogger.cpp

Public Types

Public Member Functions

Detailed Description

Member Enumeration Documentation