Peter Barker b6ee93aeef AP_Logger: change BAD_DEPTH logerror code from 0 to 3 ...

We use 0 to mean cleared for many other subsystems, so this is a bit of
a wart.

2019-03-27 12:02:53 -04:00

..

examples

…

AP_Logger_Backend.cpp

AP_Logger: use AP_InternalError for tracking internal errors

2019-03-21 21:34:33 +11:00

AP_Logger_Backend.h

AP_Logger: use AP_InternalError for tracking internal errors

2019-03-21 21:34:33 +11:00

AP_Logger_Block.cpp

…

AP_Logger_Block.h

…

AP_Logger_DataFlash.cpp

…

AP_Logger_DataFlash.h

…

AP_Logger_File.cpp

AP_Logger: use AP_InternalError for tracking internal errors

2019-03-21 21:34:33 +11:00

AP_Logger_File.h

…

AP_Logger_MAVLink.cpp

AP_Logger: use AP_InternalError for tracking internal errors

2019-03-21 21:34:33 +11:00

AP_Logger_MAVLink.h

…

AP_Logger_MAVLinkLogTransfer.cpp

…

AP_Logger_SITL.cpp

…

AP_Logger_SITL.h

…

AP_Logger.cpp

AP_Logger: move Log_Write_Error into library

2019-03-27 12:36:40 +11:00

AP_Logger.h

AP_Logger: change BAD_DEPTH logerror code from 0 to 3

2019-03-27 12:02:53 -04:00

LogFile.cpp

…

LoggerMessageWriter.cpp

AP_Logger: simplify the message writers

2019-03-24 11:45:08 +11:00

LoggerMessageWriter.h

AP_Logger: simplify the message writers

2019-03-24 11:45:08 +11:00

LogStructure.h

AP_Logger: move Log_Write_Error into library

2019-03-27 12:36:40 +11:00