Defines

System Error Log Message Types

There are four types of log entries. More...

Defines

#define  SYSLOG_ERROR   0x00000001
  An error message.
#define  SYSLOG_WARN   0x00000002
  An example of this type is a message telling the user the MAX file just loaded is obsolete and needs to be resaved.
#define  SYSLOG_INFO   0x00000004
  An example of this is a message indicating a new MAX file has been loaded.
#define  SYSLOG_DEBUG   0x00000008
  This message type is for anything you think might help trace problems that the user has with your code.
#define  SYSLOG_BROADCAST   0x00010000
#define  SYSLOG_MR   0x00020000

Detailed Description

There are four types of log entries.

In the preference dialog, the user can select what types of log entries they want to be generated. This is how users control the verbosity of the log file in some meaningful way. Developers are encouraged to be very verbose about information and debug messages -- the Log() functions should be used to record any events out of the ordinary. As the user can elect to ignore these messages they are perfect for troubleshooting. The values can be OR'd together.

SYSLOG_DEBUG messages are also always sent to the debugger output using DebugPrint()

See also:
Class LogSys

Define Documentation

#define SYSLOG_ERROR   0x00000001

An error message.

An example of this type is a fatal error. Do NOT pass in a string longer than 8192 characters when passing in this type (Otherwise you will crash).

#define SYSLOG_WARN   0x00000002

An example of this type is a message telling the user the MAX file just loaded is obsolete and needs to be resaved.

This option may not be selected by the MAX user via the UI but it is available for use (it's used internally often). A warning message.

#define SYSLOG_INFO   0x00000004

An example of this is a message indicating a new MAX file has been loaded.

An information message.

#define SYSLOG_DEBUG   0x00000008

This message type is for anything you think might help trace problems that the user has with your code.

Message will also be sent to the debugger output using DebugPrint(). A debug message.

#define SYSLOG_BROADCAST   0x00010000
#define SYSLOG_MR   0x00020000