Any alternative to d()?

[lyravega]

Is there a similar command that works like d()?

[Harven]

If you mean a command that add some text to chat window, then there is CHAT_SYSTEM:AddMessage()

[lyravega]

Yep, thanks!

[SpecialK]

A handy way for formatted print to screen with a default color; sort of C "printf()" style.

local function p(...)
   local function w(...) CHAT_SYSTEM:AddMessage("|cD8C1FF"..string.format(...).."|r") end
   local s, r = pcall(w, ...)
   if not s then error(r, 2) end
end

With the pcall() to the wrapper it will catch string.format() errors and point to the exact "p()" call where it happened (like accidentally passing a "nil" value for example). With out this setup it you'll only see the context on/inside the "p()" call it's self.

Example usage:

p("My name is \"%s\"", GetUnitName("player"))

You could add more variations of course.
Like pass a color argument instead of a default color "local function p(color, ...)", etc.

[Seerah]

Every time you call your P() function, you create a new instance of your w() function.

[zgrssd]

Originally Posted by lyravega Is there a similar command that works like d()?

If you want d() messages from before the init of chat window being shown, LibDebug can do that (it adds buffering to d() ). But right now it has minor bug with swallowed Parsing errors so it's a two edged sword for Developers till next version.

[zolan]

Originally Posted by lyravega Is there a similar command that works like d()?

I do this in my addons. It will output to whatever chat window screen that the user has open.

CHAT_SYSTEM["containers"][1]["currentBuffer"]:AddMessage('message here')

It, of course, won't work until after PLAYER_ACTIVATED is fired off, so that won't work if you are just trying to get debug info but is great for outputting stuff for the user.

~Zolan

[Seerah]

Or just

CHAT_SYSTEM:AddMessage("text")

[zolan]

Just in case this might help someone else out.. If you know the container and tab that you want to output to you can do this:

By default there is only one container, though I think there may be addons that make other containers:

containerNum = 1

And the tabs seem to be numbered from left to right so the second tab would be 2:

tabNum = 2

Using those you can output 'Ta daaaaaaa' to the first container on the 2nd tab using the following:

CHAT_SYSTEM.containers[containerNum].windows[tabNum].buffer:AddMessage('Ta daaaaaaa')

I'd be glad to know if someone comes up with a better solution than this.

~Zolan

[zgrssd]

Originally Posted by zolan I'd be glad to know if someone comes up with a better solution than this.

You should propably go up and read the post of Seraah just between your two posts. Not tried them, but I think he knows what he is saying.

[Seerah]

But Zolan's second post is for if you want to write to a tab other than the default/1st.

[zolan]

Originally Posted by Seerah But Zolan's second post is for if you want to write to a tab other than the default/1st.

Zolan's first post is to write to whatever your currently selected tab is which, I believe, is different than CHAT_SYSTEM:AddMessage()

[zolan]

Originally Posted by zgrssd You should propably go up and read the post of Seraah just between your two posts. Not tried them, but I think he knows what he is saying.

Serrah definitely knows what *she* is saying. But my first post definitely doesn't behave like d() as it adds a message to whatever your currently selected tab is.

[Seerah]

Originally Posted by zolan Zolan's first post is to write to whatever your currently selected tab is which, I believe, is different than CHAT_SYSTEM:AddMessage()

My post wasn't to correct yours, just to offer a more simplified alternative to d().

[lyravega]

So, another question about d() then.

I looked around but wasn't able to find that post again, which kinda explained how d() works. Which is faster? Adding a message through CHAT_SYSTEM directly, or d() is just a shortcut for it (no difference in between, so to speak)?

Even 1 nano-second win is important for me :P

[Seerah]

It depends on what you want printed to chat.

This is the d() function:

function d(...)    
    for i = 1, select("#", ...) do
        local value = select(i, ...)
        if(type(value) == "table")
        then
            EmitTable(value)
        else
            EmitMessage(tostring (value))
        end
    end
end

If all you want to print is simple text, then just use CHAT_SYSTEM:AddMessage("text").

Granted, you shouldn't be looking for 1 nanosecond optimizations. Good coding practices aside, only worry about optimizing when doing heavy calculations or frequent updates.

[lyravega]

True, true, but still

[zgrssd]

Originally Posted by Seerah This is the d() function: function d(...)         for i = 1, select("#", ...) do         local value = select(i, ...)         if(type(value) == "table")         then             EmitTable(value)         else             EmitMessage(tostring (value))         end     end end

Are you certain it takes any amount of parameters? When I tried to give it more then one value, it took only the first. But it could have been a fault in the override BugEater provides for d() too.

Edit: I Added the whole "how do I output to the chat" thing to the quick questions:
http://wiki.esoui.com/AddOn_Quick_Qu...to_the_chat.3F

[thelegendaryof]

Originally Posted by zgrssd a fault in the override BugEater provides for d() too.

Correct that 's long since on my todo list as in planning to move away from modifing d() to heavly
as in implementing buffers - I'm planning to write distinct debugging methods with filters next (as suggested).

Edit: Fixed it in 1.0 - R9- thanks Seerah for the provided info.

Cheers!