The DebugLogViewer relies on LibDebugLogger v1.1, so you need to make sure to update that library (update was released earlier today).

This addon is intended for both authors and regular players alike. The biggest benefit for non-authors is that it will suppress the Lua Error pop-up that could show up in the worst situations (e.g. mid combat).

The loot info should be shown in the quick log, unless you hid that window (bottom right of the screen). Maybe you can send me a screenshot or video. I'll also check out if Lui does something strange.

[quote=Anceane]The quick log can be moved, it is just "locked" by default to avoid accidentally changing its location or size. Just click the settings menu icon above the scroll bar and it will show an entry "Unlock Position". Then you can resize and move it. Afterwards you can "Lock Position" again. If you have a hard time reading the text, you can also increase the font size in the settings menu of the addon.
And last but not least, you can configure the quick log to let the shown output disappear after a specific time and remove it once it is hidden (also from the addon settings). That way you only see the newest messages in there, which may be less confusing.

If you still feel like the quick log is not for you, then you will have to wait for the next version of Debug Log Viewer. I plan to add a setting to allow configuring where the chat messages should be shown (quick log or regular chat as before). For now you can edit the file "StartUp.lua" in the DebugLogViewer folder and remove line 74 "LDL:SetBlockChatOutputEnabled(true)".

You should see the cursor change to a double arrow when you move it over the edge of the quicklog while it is unlocked. Then just click and drag to resize it as you like.

There is no way to do that aside from not using the DebugLogViewer as a user, or addon authors updating their addons to not abuse the d() debug method to print messages in chat.
The issue is that d() is a debug tool and as such DebugLogViewer will capture its output, but most addons simply abuse it to display chat messages to the user, because it happens to print the debug output in chat in the base game (although it bypasses several systems). If you have a specific addon that doesn't print to chat, you should kindly ask the author to make use of LibChatMessage to print those chat messages the proper way.

It highly depends on how the addon is written. Some just have one central place where they print their chat messages, others have the calls littered all over the place. Some prepend the message with a [Tag], others may even have some settings that affect how it works.

- adding LibChatMessage as a dependency is as simple as adding a new line
in the txt file of the addon (or just append it to the end if there is already a line with "DependsOn"). The >= 87 is optional, but tells the game to require at least a version of LibChatMessage with an "AddOnVersion" equal or higher to that number.

- Loading is not something the author has to worry about any more. The user has to ensure all required dependencies are present.

- Exchanging d() and df() is the tricky part. First you need to create a chat proxy for the addon:
Where to place that depends on the addon structure. If it only has one file you can just put it somewhere on the top. If the addon is split up into multiple files, it will have a global table with a name similar to the addon name somewhere in the lua file that is listed first in the txt. You can just assign it to that table so you have access in all other files. e.g.
and then you can assign it to a local variable in each file where it is needed:

Then you have to locate all places where d and df are used with the help of notepad++' find in files feature (ctrl+shift+f) or a similar tool. The regular expression and filtering for *.lua files should find everything in most cases. you may also need to check *.xml files in case they contain lua code.
The calls to d() have to be replaced with chat:Print() and calls to df() with chat:Printf().

After that you just need to test that everything is still working and you are done.