Ok, I've updated the GUI to be a little more user-friendly (I hope). The options are grouped up. Additionally, I've lightened up the GUI a little.
For the sake of saying so, the skins I have out will be causing some display issues with the HotKey layer in Bartender4 until BT4 gets its fix. You'll just have to deal with it until then. :P
I'm pretty sure that the issue I have is related to something out of your control and probably an older addon without new code but I'm really just looking for a little confirmation so I can find another method.
I'm using an addon that allows me to move the default Buff/Debuff/Weapon Buffs but as soon as I load it up since it is skinnable this is what I end up with. No matter what skin I use the brightness never returns until disabling BF which is not an option for me.
Since as soon as it's skinned it's nearly to dark to deal with is there anything I can do to resolve this? I apologize if this is posted somewhere else in this thread I tried to search for all the key terms that someone else might have posted with no luck.
It might help if you mentioned which addon you're using to move the buff frames, and which addon you're using to attempt to skin the buff icons (if it's not the same addon).
Sorry posted that late and I didn't even think about it. The buffs are default but movable by using femtoBuff and the BF skin is Darkinator: Matte skin
Maybe I'll just give PhanxBuffs a try it appears to do everything I need and more up to date.
The latest revision (321), no longer allows border color settings in the skins themselves, but rather uses either the Color argument passed through the Skin() method or if not passed, the old border texture's vertex color.
This will prevent action bars from having white borders on equipped items, etc, and allows for automagical border colors for debuffs, etc. (IE, you shouldn't have to pass the color if you're using the defaults as long as you're actually passing the default texture object).
I don't get any border colors with Bartender 4 (eg green for equipped items). What should I do to fix that?
Anyone else having issues with SBF and this? they were compatible last i remember, but recently they stopped working together at all (sbf doesnt show up on the list of mods in BF).
Anyone else having issues with SBF and this? they were compatible last i remember, but recently they stopped working together at all (sbf doesnt show up on the list of mods in BF).
There's more wrong than only line 3 in the BF-code from SBF.
SBF with BF r325 after login:
Resetting the colors brings back the original colors of the skin (other skins have the same problem), but only for the active buffs. The reset doesn't works for new buffs and after relogging all buffs have again the white border.
SBF has never correctly supported ButtonFacade; it's always been a half-assed hack that breaks any time anything in ButtonFacade changes. Satrina has already stated that the next major version of SBF will include proper ButtonFacade support, but I haven't seen any ETA on when that might be available.
Satrina has already stated that the next major version of SBF will include proper ButtonFacade support, but I haven't seen any ETA on when that might be available.
The BF-fix (3.1.21) was announced two month ago, and this was the last post in the comments.
The reason it's not working with SBF with newer versions is that previously, LBF didn't support border colors other than the "Equipped" border. I'm currently working better support for borders into the newer versions.
However, I don't understand why it's not showing some at least some color because the engine uses the original border color as a fall-back in case no other color is specified. I'll have to dig into SBF to find out.
Hi,
I have recently started to use SBF again, and it does not seem to be compatible with BF in that my icons sometimes randomly disappear basically everywhere, both in my inventory, in the equipment manager, spellbook and of course on my action bars. If another icon replaces the old icon then it works again, though, such as with shapeshifting which automatically got one icon for "use" and another for "not use".
While this is of course an issue on SBF's end, is there any solution to this? I very much like both addons.
I just put up revision 326. This adds support for border colors both to LibButtonFacade and the GUI. Keep in mind that any add-on that does NOT use new API for border colors WILL NOT WORK. Talk to the authors of those add-ons.
That said, for authors there's a couple of new "features". Most importantly, the Group:AddButton() method now accepts a third parameter "Type". This tells LBF exactly what type of button you're passing so that the borders can be colored accordingly. Take a look at the change log to see the various "types". And for those of you with ActionButton mods, don't worry. The default type is "Action" so you don't *have* to change anything. :p
I didn't put any API in there to change the "type" on the fly, simply because I've yet to see a need for it. If it does need something like that, let me know. For now, you can actually set it manually by adding/changing the .__LBF_Type field of the button object to the type you wish it to be. Though you'll probably have to reskin the button or group afterwards.
That brings me to another feature. Authors can now call the Group:Reskin() method which takes no parameters and simply reapplies the current settings. Think of it as a refresh for those odd times when something you do interferes with LBF. :p
P.S. Translations are need of a hefty update. >.<
Oh, yeah. One other thing. With this implementation, a savvy author could create a bar mod that actually colors the borders of a user's spells based on the spell's type. /wink
Keep in mind that any add-on that does NOT use new API for border colors WILL NOT WORK.
What exactly is the new API? The project's API documentation page hasn't been updated since July, and I don't see anything relevant in the last page in this thread.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
OK that's too bad, 'cos I love the skin on the rest of my bars.
Thanks for the response.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumFor the sake of saying so, the skins I have out will be causing some display issues with the HotKey layer in Bartender4 until BT4 gets its fix. You'll just have to deal with it until then. :P
I'm using an addon that allows me to move the default Buff/Debuff/Weapon Buffs but as soon as I load it up since it is skinnable this is what I end up with. No matter what skin I use the brightness never returns until disabling BF which is not an option for me.
Since as soon as it's skinned it's nearly to dark to deal with is there anything I can do to resolve this? I apologize if this is posted somewhere else in this thread I tried to search for all the key terms that someone else might have posted with no luck.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumMaybe I'll just give PhanxBuffs a try it appears to do everything I need and more up to date.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI don't get any border colors with Bartender 4 (eg green for equipped items). What should I do to fix that?
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse PremiumSee this post: http://forums.wowace.com/showpost.php?p=298914&postcount=883
SBF with BF r325 after login:
Resetting the colors brings back the original colors of the skin (other skins have the same problem), but only for the active buffs. The reset doesn't works for new buffs and after relogging all buffs have again the white border.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI've used the latest alpha version on the screenshot, but after this I've returned to BF 3.3.301.
The BF-fix (3.1.21) was announced two month ago, and this was the last post in the comments.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumHowever, I don't understand why it's not showing some at least some color because the engine uses the original border color as a fall-back in case no other color is specified. I'll have to dig into SBF to find out.
I have recently started to use SBF again, and it does not seem to be compatible with BF in that my icons sometimes randomly disappear basically everywhere, both in my inventory, in the equipment manager, spellbook and of course on my action bars. If another icon replaces the old icon then it works again, though, such as with shapeshifting which automatically got one icon for "use" and another for "not use".
While this is of course an issue on SBF's end, is there any solution to this? I very much like both addons.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThat said, for authors there's a couple of new "features". Most importantly, the Group:AddButton() method now accepts a third parameter "Type". This tells LBF exactly what type of button you're passing so that the borders can be colored accordingly. Take a look at the change log to see the various "types". And for those of you with ActionButton mods, don't worry. The default type is "Action" so you don't *have* to change anything. :p
I didn't put any API in there to change the "type" on the fly, simply because I've yet to see a need for it. If it does need something like that, let me know. For now, you can actually set it manually by adding/changing the .__LBF_Type field of the button object to the type you wish it to be. Though you'll probably have to reskin the button or group afterwards.
That brings me to another feature. Authors can now call the Group:Reskin() method which takes no parameters and simply reapplies the current settings. Think of it as a refresh for those odd times when something you do interferes with LBF. :p
P.S. Translations are need of a hefty update. >.<
Oh, yeah. One other thing. With this implementation, a savvy author could create a bar mod that actually colors the borders of a user's spells based on the spell's type. /wink
What exactly is the new API? The project's API documentation page hasn't been updated since July, and I don't see anything relevant in the last page in this thread.