(not sure where to post this since it covers at least 3 addons, so I'm posting it in HELP! I hope the right people see it)
Tried using Fortress+FuBar2Broker and StatBlockCore+FuBar2Broker. Following is a list of observations from a tester point of view:
1. Issues common to Fortress and SBC:
1a. I can't change the icon size; it's way too large by default.
1b. I can't change overall "block" scale. It seems that reducing the text size doesn't reduce the block size accordingly, probably partially because of the large icon size.
1c. There is a *huge* amount of whitespace around the text and/or icon that cannot be reduced via configuration options.
This is making all of my plugins take up a large amount of screen space, preventing me from sticking my FuBar plugin displays together in a way that takes up approximately the same amount of space as they did in FuBar.
2. I think the following issues may be related more to FuBar2Broker r78418:
2a. Tooltips for some addons (AuldLangSyneFu, FactionsFu, Auditor, and others) are displayed both at a MUCH larger scale than they were under FuBar, and also directly on top of the plugin display block. This makes the plugin impossible to move away from its default location in the center of the screen, since the tooltip completely obscures it.
2b. MagicTargets, RBM, NShakedown, ButtonFacade, Omen and probably other addons don't seem to get scooped up by F2B, and instead display as minimap icons. This probably isn't F2B's fault so much as those addons' but it is still a tad disappointing.
2c. Creating an Ace3Config entry for each FuBar plugin seems to slow down Ace3Config immensely. It would be nice if it could somehow have a sub-list under FuBar2Broker or something, but I'm sure that'd be too kludgy and/or difficult to program.
3. Fortress r78592-specific issues:
3a. Having to either select "use master settings" for each plugin to get the color and font settings, or configure those settings for each plugin is a bit clunky. The clunkiness of configuration is also compounded by the fact that the showing of label/icon/etc. is also tied to master settings.
4. SBC r78579-specific issues:
4a. I am unable to access plugin-specific Ace3Config menus for FuBar plugins displayed via FuBar2Broker. Attempting to select them from the Ace3Config addon list generates UI errors instead.
2b. MagicTargets, RBM, NShakedown, ButtonFacade, Omen
i know for sure that Omen and RBM don't actualy use "FuBarPlugin" version 2 (Ace2) or version 3 (Rock) but instead use a Modified version of the Lib that is Framework independant. That could explain why they are not being picked up.
Altho i'd recommend that these addons, as they are in common use and development, use LDB directly instead of trying to get FuBar2LDB to compensate for it.
I ll add a frew more things (using Fortress/FuBar2Broker only here):
- Violation and MoneyFu generate an error (i ll link the bugsack when i can) when starting the game. But after this, they are working fully.
- Manufac has no icon displayed and the left click action doesnt work
- PerformanceFu has some weird issue with the tooltip : contrary to other Fu converted add ons (like Closetgnome one), the tooltip disappear when you mouse over the tooltip itself and as such you cant scroll the tooltip with the mouse wheel.
- Broker_Durability doesnt seem to work most of the time : either it gives some silly value (like -2xxxxxxxx %) or it doesnt seem up to date at all.
Thats all for now, keep up the good work guys :)
Edit (bugsack):
FuBar_MoneyFu-20400-1\MoneyFu.lua:335: attempt to perform arithmetic on field '?' (a nil value)
AceAddon-2.0-57245 (Ace2):926: in function <Interface\AddOns\Ace2\AceAddon-2.0\AceAddon-2.0.lua:919>
<in C code>: ?
AceEvent-2.0-66043 (Ace2):260: in function `TriggerEvent'
AceEvent-2.0-66043 (Ace2):910: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:903>
Violation-1.0.74674\Violation.lua:1316: attempt to index upvalue 'db' (a nil value)
AceAddon-2.0-57245 (Ace2):926: in function <Interface\AddOns\Ace2\AceAddon-2.0\AceAddon-2.0.lua:919>
<in C code>: ?
AceEvent-2.0-66043 (Ace2):260: in function `TriggerEvent'
AceEvent-2.0-66043 (Ace2):910: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:903>
FuBar_PerformanceFu-2.076217\PerformanceFu.lua:412: attempt to perform arithmetic on upvalue 'currentMemory' (a nil value)
AceAddon-2.0-57245 (Ace2):495: in function <Interface\AddOns\Ace2\AceAddon-2.0\AceAddon-2.0.lua:488>
AceAddon-2.0-57245 (Ace2):617: in function `InitializeAddon'
AceAddon-2.0-57245 (Ace2):484: in function <Interface\AddOns\Ace2\AceAddon-2.0\AceAddon-2.0.lua:461>
<in C code>: ?
AceEvent-2.0-66043 (Ace2):298: in function `TriggerEvent'
AceEvent-2.0-66043 (Ace2):910: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:903>
<in C code>: ?
<in C code>: in function `pcall'
FuBar-3.0.52967\FuBar.lua:829: in function <Interface\AddOns\FuBar\FuBar.lua:824>
FuBar-3.0.52967\FuBar.lua:957: in function `LoadPlugin'
FuBar-3.0.52967\FuBar.lua:1093: in function `object_method'
LibRockTimer-1.0-1118 (LibRockTimer-1.0):289: in function <...terface\AddOns\LibRockTimer-1.0\LibRockTimer-1.0.lua:227>
Manufac-2.0.r55252\Manufac.lua:784: Dewdrop-2.0: Bad argument #2 to `Open' (table or string expected, got nil)
Ace2\AceLibrary\AceLibrary.lua:122: in function <Interface\AddOns\Ace2\AceLibrary\AceLibrary.lua:75>
(tail call): ?:
Dewdrop-2.0-56529 (DewdropLib):2950: in function `Open'
Manufac-2.0.r55252\Manufac.lua:784: in function `OnClick'
FuBar2Broker-1.0\FuBar2Broker.lua:146: in function <Interface\AddOns\FuBar2Broker\FuBar2Broker.lua:142>
The solution problem 2a: with StatBlockCore it's simple: type /sbc and manually move up the blocks; I changed the y value from 550 to 850 and it worked. With Fortress you have to make a trick: move a block near the unmovable plugin, sticky them together and the move up :) After that you can move them individually with Ctrl.
The solution problem 2a: with StatBlockCore it's simple: type /sbc and manually move up the blocks; I changed the y value from 550 to 850 and it worked.
Ah. I wasn't able to get to individual plugins' settings because I was trying to do so via /ace3 instead of /sbc (see 4a in my original post).
With Fortress you have to make a trick: move a block near the unmovable plugin, sticky them together and the move up :) After that you can move them individually with Ctrl.
All the things you said SBC lacks are basically available via the plugins specific options. Typing /sbc tells you how to change the width to avoid whitespace, and changing scale will change block + icon scale.
All the things you said SBC lacks are basically available via the plugins specific options. Typing /sbc tells you how to change the width to avoid whitespace, and changing scale will change block + icon scale.
Thanks. I guess it was my bad for assuming /ace3 would work instead of trying /sbc (see 4a in my original post - hooray for a cenralized config menu system that doesn't work right for many Ace3 addons). I thought I wouldn't be able to access settings for anything but SBC itself via /sbc.
Also, the idea of having to set scaling and whitespace for each one of my two dozen fubar plugins instead of globally sounds very daunting. Ideally it would be nice to be able to initially scale everything down via global settings to the general ballpark of where I want them, then I can start tweaking individual plugin settings if needed.
Unfortunately I designed the defaults around my most common standard blocks since I barely use any FuBar blocks. I don't think it would be better to design it around the FuBar blocks (especially considering it's a hack anyway :p)
All the things you said SBC lacks are basically available via the plugins specific options. Typing /sbc tells you how to change the width to avoid whitespace, and changing scale will change block + icon scale.
I don't see anything about how to "change the width to avoid whitespace." I have a ton of whitespace to the right of my Omen icon after having cleared out its display text field.
I don't see anything about how to "change the width to avoid whitespace." I have a ton of whitespace to the right of my Omen icon after having cleared out its display text field.
Hmm, well I'm going to call poor design on that one then; it's expected that a slash command would open a menu, or to get feedback in a chat frame, but not both :p I was looking on the menu for the info. I'll check in the chat frame when I get around to testing again.
The good news is I was able to scale icons and text, so I may actually be able to use SBC as something close to a workable FuBar replacement with some fiddling.
Oh, there's options for SBC that only show in chat and not in the window? Darn you, Funky, I didn't see those either. :( Now I'll have to try it again. :P
Tried using Fortress+FuBar2Broker and StatBlockCore+FuBar2Broker. Following is a list of observations from a tester point of view:
This is making all of my plugins take up a large amount of screen space, preventing me from sticking my FuBar plugin displays together in a way that takes up approximately the same amount of space as they did in FuBar.
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumi know for sure that Omen and RBM don't actualy use "FuBarPlugin" version 2 (Ace2) or version 3 (Rock) but instead use a Modified version of the Lib that is Framework independant. That could explain why they are not being picked up.
Altho i'd recommend that these addons, as they are in common use and development, use LDB directly instead of trying to get FuBar2LDB to compensate for it.
- Violation and MoneyFu generate an error (i ll link the bugsack when i can) when starting the game. But after this, they are working fully.
- Manufac has no icon displayed and the left click action doesnt work
- PerformanceFu has some weird issue with the tooltip : contrary to other Fu converted add ons (like Closetgnome one), the tooltip disappear when you mouse over the tooltip itself and as such you cant scroll the tooltip with the mouse wheel.
- Broker_Durability doesnt seem to work most of the time : either it gives some silly value (like -2xxxxxxxx %) or it doesnt seem up to date at all.
Thats all for now, keep up the good work guys :)
Edit (bugsack):
Ah. I wasn't able to get to individual plugins' settings because I was trying to do so via /ace3 instead of /sbc (see 4a in my original post).
That certainly sounds annoying.
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorThanks. I guess it was my bad for assuming /ace3 would work instead of trying /sbc (see 4a in my original post - hooray for a cenralized config menu system that doesn't work right for many Ace3 addons). I thought I wouldn't be able to access settings for anything but SBC itself via /sbc.
Also, the idea of having to set scaling and whitespace for each one of my two dozen fubar plugins instead of globally sounds very daunting. Ideally it would be nice to be able to initially scale everything down via global settings to the general ballpark of where I want them, then I can start tweaking individual plugin settings if needed.
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorThanks
I don't see anything about how to "change the width to avoid whitespace." I have a ton of whitespace to the right of my Omen icon after having cleared out its display text field.
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorIf you use /sbc to access the menu it tells you.
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorYou use the mousewheel over an unlocked block.
Watch the chatframe ;)
Hmm, well I'm going to call poor design on that one then; it's expected that a slash command would open a menu, or to get feedback in a chat frame, but not both :p I was looking on the menu for the info. I'll check in the chat frame when I get around to testing again.
The good news is I was able to scale icons and text, so I may actually be able to use SBC as something close to a workable FuBar replacement with some fiddling.
-
View User Profile
-
View Posts
-
Send Message
Forum Moderator-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorThen make it working in the beta too :P I hate the white background, and I'm too lazy to manually edit the SV file.