RiveLog

RiveLog allows configuring logging within Rive.

By default, it uses NoOpLogger, which does nothing. You can set your own logger by assigning an instance of Logger to RiveLog.logger. For basic logging, you can use RiveLog.LogcatLogger to log to Logcat.

Types

LogcatLogger

class LogcatLogger : RiveLog.Logger

Implementation that logs to Logcat with lazy msg() evaluation.

Logger

interface Logger

Interface for logging. Implementations should provide methods for different log levels.

NoOpLogger

object NoOpLogger : RiveLog.Logger

Implementation that logs nothing. Used by default.

Properties

logger

@Volatile

var logger: RiveLog.Logger

The current logging implementation. Apps can override this to provide their own logging. For example, in your Application's onCreate:

Functions

@JvmStatic

inline fun d(tag: String, noinline msg: () -> String)

@JvmStatic

inline fun e(tag: String, t: Throwable? = null, noinline msg: () -> String)

@JvmStatic

inline fun i(tag: String, noinline msg: () -> String)

logD

@JvmStatic

fun logD(tag: String, msg: String)

logE

@JvmStatic

fun logE(tag: String, msg: String)

logI

@JvmStatic

fun logI(tag: String, msg: String)

logV

@JvmStatic

fun logV(tag: String, msg: String)

JNI bridge methods that take a String directly instead of a lambda. These are used by the C++ helper for efficient logging from native code.

logW

@JvmStatic

fun logW(tag: String, msg: String)

@JvmStatic

inline fun v(tag: String, noinline msg: () -> String)

@JvmStatic

inline fun w(tag: String, noinline msg: () -> String)