WowAce

------------------------------------------------------------------------
r202 | funkydude | 2013-11-28 14:15:50 +0000 (Thu, 28 Nov 2013) | 1 line
Changed paths:
   M /trunk/!BugGrabber.toc
   M /trunk/load.xml

poke to wake Curse Client.
------------------------------------------------------------------------
r201 | funkydude | 2013-11-28 03:43:26 +0000 (Thu, 28 Nov 2013) | 1 line
Changed paths:
   M /trunk/BugGrabber.lua

Only allow 1 ADDON_ACTION_FORBIDDEN per addon to prevent in-combat message spam by certain unavoidable Blizz taint messages.
------------------------------------------------------------------------
r200 | funkydude | 2013-11-19 17:40:59 +0000 (Tue, 19 Nov 2013) | 1 line
Changed paths:
   M /trunk/BugGrabber.lua

Don't bother running the stanizeStack func, should probably leave that to display addons. Hopefully also cuts down on the chances of a script too long for some users.
------------------------------------------------------------------------
r199 | mikk | 2013-11-18 22:46:09 +0000 (Mon, 18 Nov 2013) | 4 lines
Changed paths:
   M /trunk/BugGrabber.lua

http://www.wowace.com/addons/bug-grabber/tickets/59-bug-grabber-completely-disables-itself-if-more-than/
BugGrabber will now re-enable itself after hitting the 10 messages/sec limit and not stay disabled indefinitely.... and if that wasn't the purpose, back out the changes and I'll know to switch to (and recommend) something else.
 
I also changed the mechanic from OnUpdate-based clamping (which actually lets 8324983745345 messages through during the first second) to clamping in the error grabber - which also has the benefit of spending CPU only when it needs to be spent (when something is erroring).
------------------------------------------------------------------------