All buffers should implement this interface. They all need the three basic methods:
log(), flush() and clear(). Log is the most important and it's the one that is used the most
Clear should clean the internal buffer, if you implement one.
LaoBuffers are usually registered to listen for a Laologger event. One buffer can listen to several LaoLoggers
public function log(evtObj:Object):VoidLog is the most important. it's the one that handles log messages. That's why the methods of this class aren't used directly, but through a LaoLogger.
evtObj | is an object received from a Laologger "log" event. If you want to use this
method directly anyway, the evtObj should have the following properties: target:a reference to the movie/object that is triggering the log action type::must be equal to "log" argument: an instance of a LaoEvent |
public function flush(evtObj:Object):VoidYou could implement an internal buffer that stores all log messages until you call this method, which should take care of publishing the internal buffer and clearing it after it's done. It's the method called by a LaoEvent when you ask it to flushBuffers.
evtObj | is an object received from a Laologger "flush" event. If you want to use this
method directly anyway, the evtObj should have the following properties: target:a reference to the movie/object that is triggering the log action type::must be equal to "flush" argument: an instance of a LaoEvent |
public function clear(evtObj:Object):VoidIf you implement an internal buffer that stores all log messages, this method should be used to clear it whenever you need to. It's the method called by a LaoEvent when you ask it to flushBuffers.
evtObj | is an object received from a Laologger "flush" event. If you want to use this
method directly anyway, the evtObj should have the following properties: target:a reference to the movie/object that is triggering the log action type::must be equal to "clear" argument: an instance of a LaoEvent |