I don't mind the move to LDB, but why were the slash commands taken out? I always used to hide the fubar thing and use the slash cmd to check the bug list or reset it. Please consider re-enableing the slash commands.
I'm confused, why is ther eno support for Fubar and minimap anymore? I have to get another addon just to make bugsack/buggrabber work now?
BugSack is working, but it has no FuBarPlugin support - so you have to install Barrel (for minimap icon), or Broker2FuBar, or a Broker-display (Fortress, StatBlockCore, Carousel, Titan).
I can understand removing FuBar support, as not everyone uses that. But removing it from the minimap is just asinine; means I can never load JUST BugSack/BugGrabber and one other addon and see what errors it kicks.
I can understand removing FuBar support, as not everyone uses that. But removing it from the minimap is just asinine; means I can never load JUST BugSack/BugGrabber and one other addon and see what errors it kicks.
Is there any way to make it so it goes to the minimap on default, and is moved OFF by another addon (Fortress, FuBar, anyotheraddonthatdoesthesamekindofthing)?
No. The idea of using LibDataBroker is to let the user choose how its icon shows up by installing a display addon like those that Ydrisselle listed. Get Barrel if you want it to show up as a minimap icon. Get ButtonBin if you want it to show up on a MinimapButtonBag type of collapsable list. Get Fortress, SBC, Titan, or FuBar+Broker2FuBar if you want it to show up on a bar/block. The choice is yours, it just takes the installation of one additional addon :p
Is there any way to make it so it goes to the minimap on default, and is moved OFF by another addon (Fortress, FuBar, anyotheraddonthatdoesthesamekindofthing)?
Sure, if Rabbit wants to add more code just to facilitate a minimap. I recommend Barrel.
I'm using ButtonBin as a FuBar replacement. Three bars at the top to mimic the left/right/center behavior.
Not really the same thing because ButtonBin is really only for launchers, so it shows icons but not any text label data they might supply. But if it works for you then that's all that matters :)
Currently I'm using ButtonBin for most stuff, and Fortress for picoDPS.
Not really the same thing because ButtonBin is really only for launchers, so it shows icons but not any text label data they might supply. But if it works for you then that's all that matters :)
Currently I'm using ButtonBin for most stuff, and Fortress for picoDPS.
I have labels and/or icons in ButtonBin. It's all under the options for the individual bins. The only problem I have with it is the fact that you can't customize each dataobject by way of turning off text on one or removing the icon on another. I have one bin that's hidden until mouseover that's all icons. My top bar has icons and labels (there are some I'd like to only have labels but, as before, there's not yet a per-button configuration).
For launchers, I use MakeRocketGoNow. I also have a square show-on-mouseover ButtonBin that handles icon-only FuBar2Broker plugins.
Quote: Originally Posted by ant1pathy I can understand removing FuBar support, as not everyone uses that. But removing it from the minimap is just asinine; means I can never load JUST BugSack/BugGrabber and one other addon and see what errors it kicks.
The minimap button was a FuBarPlugin feature.
But FuBarPlugin was bundled/embedded with BugSack. We were able to use it just fine without ever having FuBar installed. Now it no longer Just Works; now users are required to be aware that BugSack is no longer a "front end" to BugGrabber, but rather an inaccessible middle layer (which rather raises the question, what's the point? why bother with really nice and readable formatting if you can't easily see it?)
At the very least, give us a slash command back. That way we can continue to actually use BugSack -- especially important at this time of constant addon flux and debugging of a new patch -- while those of us who had never heard of "LDB" before today work out which of the new front ends we prefer.
edit: the reason I'm semi-ranting and more than semi-annoyed is, like Panzerdoll says a couple posts down, this was all yanked out from under us with no warning, often while we were trying to update and debug other addons. Again, please, just give some slash command to view the frame and we'll find a "pretty" interface later.
The problem I have is I'm pretty sure I was using r158 yesterday evening and it was working fine with Fubar. I updated to a newer version today and no Fubar *and* no slash commands. So I try both Buttonbin and Fortress, Bugsack shows up in neither one. I've tried reverting to r158 (which is the version on WoWInterface) to no avail.
I don't really care about databroker vs fubar or whatever. I don't care about having a minimap icon if I could at least open the frame with a slash command.
Get Barrel if you want it to show up as a minimap icon.
Amusingly, the current version of Barrel handles Omen and Bartender4, but throws errors with the current version of BugSack. At least BugSack still captures them correctly though!
[2008/10/15 15:59:56-2-x13]: Barrel-0.1\Core.lua:306: attempt to index local 'dataobj' (a nil value)
Barrel-0.1\Core.lua:265: in function `UpdatePosition'
Barrel-0.1\Config.lua:94: in function <Interface\AddOns\Barrel\Config.lua:92>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[2]":9: in function <[string "safecall Dispatcher[2]"]:5>
(tail call): ?:
AceConfigDialog-3.0\AceConfigDialog-3.0.lua:781: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:600>
AceConfigDialog-3.0\AceConfigDialog-3.0.lua:829: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:821>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[3]":9: in function <[string "safecall Dispatcher[3]"]:5>
(tail call): ?:
AceGUI-3.0\AceGUI-3.0.lua:264: in function `Fire'
Ace3\AceGUI-3.0\widgets\AceGUIWidget-Slider.lua:47: in function <...dOns\Ace3\AceGUI-3.0\widgets\AceGUIWidget-Slider.lua:40>
---
But FuBarPlugin was bundled/embedded with BugSack. We were able to use it just fine without ever having FuBar installed. Now it no longer Just Works; now users are required to be aware that BugSack is no longer a "front end" to BugGrabber, but rather an inaccessible middle layer (which rather raises the question, what's the point? why bother with really nice and readable formatting if you can't easily see it?)
FuBarPlugin is a hell of a lot of memory/CPU overhead for a minimap button. FuBar itself requires addons to use it in order for them to be displayed. What LibDataBroker did was remove the display-dependence from the addon without incurring nearly as much memory/CPU cost. You can still have a minimap-icon with an LDB-plugin - Barrel is such an LDB-display.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
You need an LDB plugin display (like Fortress, Databroker et al) to show it.
Why? Is this just a temporary thing or a permanent change?
BugSack is working, but it has no FuBarPlugin support - so you have to install Barrel (for minimap icon), or Broker2FuBar, or a Broker-display (Fortress, StatBlockCore, Carousel, Titan).
The minimap button was a FuBarPlugin feature.
Is there any way to make it so it goes to the minimap on default, and is moved OFF by another addon (Fortress, FuBar, anyotheraddonthatdoesthesamekindofthing)?
Sure, if Rabbit wants to add more code just to facilitate a minimap. I recommend Barrel.
I'm using ButtonBin as a FuBar replacement. Three bars at the top to mimic the left/right/center behavior.
Not really the same thing because ButtonBin is really only for launchers, so it shows icons but not any text label data they might supply. But if it works for you then that's all that matters :)
Currently I'm using ButtonBin for most stuff, and Fortress for picoDPS.
I have labels and/or icons in ButtonBin. It's all under the options for the individual bins. The only problem I have with it is the fact that you can't customize each dataobject by way of turning off text on one or removing the icon on another. I have one bin that's hidden until mouseover that's all icons. My top bar has icons and labels (there are some I'd like to only have labels but, as before, there's not yet a per-button configuration).
For launchers, I use MakeRocketGoNow. I also have a square show-on-mouseover ButtonBin that handles icon-only FuBar2Broker plugins.
But FuBarPlugin was bundled/embedded with BugSack. We were able to use it just fine without ever having FuBar installed. Now it no longer Just Works; now users are required to be aware that BugSack is no longer a "front end" to BugGrabber, but rather an inaccessible middle layer (which rather raises the question, what's the point? why bother with really nice and readable formatting if you can't easily see it?)
At the very least, give us a slash command back. That way we can continue to actually use BugSack -- especially important at this time of constant addon flux and debugging of a new patch -- while those of us who had never heard of "LDB" before today work out which of the new front ends we prefer.
edit: the reason I'm semi-ranting and more than semi-annoyed is, like Panzerdoll says a couple posts down, this was all yanked out from under us with no warning, often while we were trying to update and debug other addons. Again, please, just give some slash command to view the frame and we'll find a "pretty" interface later.
I don't really care about databroker vs fubar or whatever. I don't care about having a minimap icon if I could at least open the frame with a slash command.
Amusingly, the current version of Barrel handles Omen and Bartender4, but throws errors with the current version of BugSack. At least BugSack still captures them correctly though!
Still, better than nothing!
FuBarPlugin is a hell of a lot of memory/CPU overhead for a minimap button. FuBar itself requires addons to use it in order for them to be displayed. What LibDataBroker did was remove the display-dependence from the addon without incurring nearly as much memory/CPU cost. You can still have a minimap-icon with an LDB-plugin - Barrel is such an LDB-display.