| Backend API |
Adirelle |
Adirelle |
28 Feb 2009 |
| These methods are intended for use by LigDebugLog backends, i.e. addons that receive and display as they need the debug log generated by the loggers. Library API :IterateLoggers( [ onlyNamed ] ) Returns a triplet usable in a for statement to iterate all registered loggers. If onlyNamed is true, only loggers containing a name attribute are listed. for logger, name in LibStub('LibDebugLog-1.0'):IterateLoggers(true) do DoSomethingUsefulWith(logger, name) end Callbacks NewLogger Fired when a new... |
| Logger API |
Adirelle |
Adirelle |
09 Oct 2008 |
| This API is available by embedding LibDebugLog-1.0 into your addon or any table you want. It makes the target a "logger". Embedding Using AceAddon-3.0 local addon = LibStub('AceAddon-3.0'):new('MyAddon', 'LibDebugLog-1.0') function addon:SomeMethod() self:Debug('We are in SomeMethod') end Manual embedding local t = {} LibStub('LibDebugLog-1.0'):Embed(t) t:Debug('Debug !') Mixin API :Debug( msg [, ...] ) Sends a debug log message. msg is converted to string. If more arguments are provided,... |
| Main |
Adirelle |
Adirelle |
09 Oct 2008 |
| LibDebugLog-1.0 aims at providing a simple debug API. By default, all messages are printed to the default chat frame. But as soon as one MessageLogged callback is registered, the library becomes quiet and sends all messages through this way. Logger API Backend API DebugLogBackend is an example of backend. Note: the standalone version ships with a little code stub that makes the debugging setting persistent through sessions. |
