I am getting this error consistently on a full copy of BugSack (downloaded from wowace, the 3.0-beta2 version with libraries included and embedded.
-----------------
[2008/10/16 13:51:30-7679-x1]: BugSack-2.x.x.152\BugSack.lua:374: attempt to call field 'RegisterCallback' (a nil value)
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[1]":9: in function <[string "safecall Dispatcher[1]"]:5>
(tail call): ?:
AceAddon-3.0\AceAddon-3.0.lua:365: in function `EnableAddon'
AceAddon-3.0\AceAddon-3.0.lua:435: in function <Interface\AddOns\Ace3\AceAddon-3.0\AceAddon-3.0.lua:421>
<in C code>: in function `LoadAddOn'
Interface\FrameXML\UIParent.lua:991: in function `UIParentLoadAddOn':
Interface\FrameXML\UIParent.lua:241: in function `CombatLog_LoadUI':
Interface\FrameXML\UIParent.lua:389: in function `UIParent_OnEvent':
<string>:"*:OnEvent":1: in function <[string "*:OnEvent"]:1>
Everything works good for me, but how do I get it to stop saying "Fatality" when I log in?
In the dropdown menu, there's an option for sound (I can't remember exactly what it's called). Set the sound to "None" and then it'll no longer play a sound when an error occurs.
I'm not sure if I'm the only one, however I don't believe that with the new version for 3.0.2, you can configure Bugsack. There is no fubar option, nor is there any /commands for it... But yes, had it been working (at least in my case) you could configure the sound that played when an error had occurred.
I meant the bugsack commands, not buggrabber. I used to use /bugsack show all and /bugsack reset ... and they don't seem to exist anymore.
There has been a lot of response concerning Fubar and minimap buttons but no one has answered this. Personally I prefer slash commands over mouse clicks.
I understand removing fubar/minimap support, but I don't understand why the /bugsack slash commands don't work either.
There has been a lot of response concerning Fubar and minimap buttons but no one has answered this. Personally I prefer slash commands over mouse clicks.
I understand removing fubar/minimap support, but I don't understand why the /bugsack slash commands don't work either.
Rabbit likes the occasional bitchfest? I dunno. Makes no sense to me, but then again: I didn't write it. :D
There has been a lot of response concerning Fubar and minimap buttons but no one has answered this. Personally I prefer slash commands over mouse clicks.
I understand removing fubar/minimap support, but I don't understand why the /bugsack slash commands don't work either.
Minimap support is back with the new LDBIcon library.
Minimap support is back with the new LDBIcon library.
However, cjsully wants the /commands back. I, also, am interested in why they were removed. I don't always want to thumb my trackball up to the icon to do something. I can, when I feel the urge, type more rapidly.
The reason the slash command is gone at the moment is because I can't use the same option table to create a AceCmd-3.0 slash command and a Dewdrop-2.0 dropdown.
That said, I will add a slash command, just hang on (actually, I just added a temporary one to toggle the minimap icon, don't let that one fool you).
The BugSack v3.0-beta3 ZIP is not packed with all the libraries it needs to function on its own (in combination with !BugGrabber v3.0-beta2).
Functioning on their own on a test character to try out the new LibDBIcon library. The full contents of the BugSack-3.0-beta3.zip file (libraries & all) was installed. Error on logon (in BugGrabber's saved variables file, the BugSack GUI never appeared):
BugSack-3.0\\BugSack.lua:40: Cannot find a library instance of \"AceAddon-3.0\".\n!BugGrabber-2.2\\libs\\LibStub\\LibStub.lua:23: in function `LibStub'\nBugSack-3.0\\BugSack.lua:40: in main chunk
Then afterwards enabled the standalone "Ace3" r706 I have installed. On relogging, BugSack loaded without errors (& with its GUI).
sometimes after a reload the tooltip do not display (using latest bugsack/buggrabber) with latest StatBlockCore. (but the tooltip of other block do appear)
The BEST idea would be to add LDB support to FuBar. Most of the other display mods (Titan included) support it. That would eliminate most of the problems.
I mean no offense Rabbit, had BugSack been improved?I installed in last night with ButtonBin, but was late.
I am also having the same issue as Xinhuan.
In the dropdown menu, there's an option for sound (I can't remember exactly what it's called). Set the sound to "None" and then it'll no longer play a sound when an error occurs.
Hey rabbit can you have a look at my post on automated error reported, and post your thoughts.
http://forums.wowace.com/showthread.php?t=14479
There has been a lot of response concerning Fubar and minimap buttons but no one has answered this. Personally I prefer slash commands over mouse clicks.
I understand removing fubar/minimap support, but I don't understand why the /bugsack slash commands don't work either.
Rabbit likes the occasional bitchfest? I dunno. Makes no sense to me, but then again: I didn't write it. :D
Minimap support is back with the new LDBIcon library.
However, cjsully wants the /commands back. I, also, am interested in why they were removed. I don't always want to thumb my trackball up to the icon to do something. I can, when I feel the urge, type more rapidly.
That said, I will add a slash command, just hang on (actually, I just added a temporary one to toggle the minimap icon, don't let that one fool you).
Functioning on their own on a test character to try out the new LibDBIcon library. The full contents of the BugSack-3.0-beta3.zip file (libraries & all) was installed. Error on logon (in BugGrabber's saved variables file, the BugSack GUI never appeared):
BugSack-3.0\\BugSack.lua:40: Cannot find a library instance of \"AceAddon-3.0\".\n!BugGrabber-2.2\\libs\\LibStub\\LibStub.lua:23: in function `LibStub'\nBugSack-3.0\\BugSack.lua:40: in main chunk
Then afterwards enabled the standalone "Ace3" r706 I have installed. On relogging, BugSack loaded without errors (& with its GUI).
BugSack includes a FuBar plugin that displays the last 5 errors in the tooltip
Not anymore! The soft requirements on LDB frontends or FuBar2whatever is not mentioned either.
"Why doesn't someone ELSE make it happen?" <- there. fixed.
Quit bitching about it, and go do it.
<- doesn't -use- fubar, so don't ask me to do it.
If you use it, and you want feature X, put it in. After all, we're all developers here, right?
break19