github
Advanced Search
  • Home
  • Pricing and Signup
  • Explore GitHub
  • Blog
  • Login

tekkub / tekdebug

  • Admin
  • Watch Unwatch
  • Fork
  • Your Fork
  • Pull Request
  • Download Source
    • 3
    • 0
  • Source
  • Commits
  • Network (0)
  • Issues (1)
  • Downloads (4)
  • Wiki (1)
  • Graphs
  • Branch: master

click here to add a description

click here to add a homepage

  • Branches (1)
    • master ✓
  • Tags (4)
    • 666
    • 3.0.1.3-Beta
    • 3.0.1.2-Beta
    • 2.3.3.1-Beta
Sending Request…
Click here to lend your support to: tekdebug and make a donation at www.pledgie.com ! Edit Pledgie Setup

Pledgie Donations

Once activated, we'll place the following badge in your repository's detail box:
Pledgie_example
This service is courtesy of Pledgie.

WoW Addon - Debug output frame thing — Read more

  cancel

http://www.tekkub.net/

  cancel
  • Private
  • Read-Only
  • HTTP Read-Only

This URL has Read+Write access

Merge commit '3.0.1.3-Beta' 
tekkub (author)
Sat Aug 30 17:16:56 -0700 2008
commit  bf2889b2108cc9e55f93d52bd374cfcae52b0f1a
tree    f5d7f0139e30dd1953635ac871c890eed52b24f1
parent  5f82bc1445b2e5eac590bdd95cb5e1830a029403 parent  b8929678acf690105577cfffa4fc58427f59c9bf
tekdebug /
name age
history
message
file LibStub.lua Sat Aug 23 12:48:23 -0700 2008 Forgot LibStub [tekkub]
file README.textile Loading commit data...
file changelog.txt Sat Aug 30 17:16:49 -0700 2008 Update changelog for 3.0.1.3-Beta [tekkub]
file tekDebug.lua Sun Jul 27 16:15:52 -0700 2008 Remove OH and Dongle, completely standalone now... [tekkub]
file tekDebug.toc Sat Aug 23 12:48:36 -0700 2008 TOC metadata [tekkub]
file tekPanelAuction.lua Sat Aug 30 17:16:15 -0700 2008 Embed update [tekkub]
README.textile

tekDebug is a debug output addon for developers. It provides a handy place to dump debug output for your addon, without spamming the chatframes of your users. To see debug output, the user must install tekDebug.

Adding support to your addon

So how do you use this bugger with your addon? simple!

local f = tekDebug:GetFrame(“MyAddon”)

This gets you a ScrollingMessageFrame to output debuggery into. You can call f:AddMessage(...) directly if you like, pass it off to your Debug lib, whatever.

In my addons this is what I do…

Force tekDebug to load before the addon, if present:

## OptionalDeps: tekDebug

Then make a Debug function (note, this version is NOT nil-safe)

local debugf = tekDebug and tekDebug:GetFrame(“MyAddon”)
local function Debug(…) if debugf then debugf:AddMessage(string.join(", ", …)) end end

Or, if you use Dongle:

MyAddon = DongleStub(“Dongle-1.0”):New(“MyAddon”)
if tekDebug then MyAddon:EnableDebug(1, tekDebug:GetFrame(“MyAddon”)) end

Accessing the output

Now that you’ve got your debug redirected, how do you view it? If you use an LDB quicklauncher addon, you’ll get a launcher there. Otherwise, you can just type /tekdebug or /td

Links

Visit my site for more info.
Please report all bugs and feature requests to my Google Code tracker
Please direct all feedback and questions to my Google Groups mailinglist.

Blog | Support | Training | Contact | API | Status | Twitter | Help | Security
© 2010 GitHub Inc. All rights reserved. | Terms of Service | Privacy Policy
Powered by the Dedicated Servers and
Cloud Computing of Rackspace Hosting®
Dedicated Server