Authors CurseForge

Geez! Can't a guy get off work first? :p It's alpha, if it don't work, don't use it! ;)

Edit. I had it fixed, just .. yeah. Ok. >.<

Edit: I've got more changes coming, so just use the latest alpha for now. Been working many hours. :(

Huh? The repository checks for syntax errors? o.O

I need to replace/remove my keyboard cover. Hit tab, get tilde. /sigh

Revision 339 should fix the issue with the Blizzard skin not showing up in the UI (BAD STORM!) and a few other minor issues.

I need some opinions on how to best go about supporting the new "Flash" frames. The problem is that they're created dynamically so I don't want to have to fool with hooking some internal function just to keep them updated. Not to mention, I'd have to figure out which group the button that's receiving the frame belongs to.

How about if I provide a method that allows the mod authors to pass the frames to LBF as they're created?

Something along the lines of:

LBF:SkinFlashAlertFrame({object},{LBFGroup})

This would probably work for LAB, as well. Of course, I'm still undecided on where to simply allow a specific "Shape" attribute (which I'd have to provide some default textures) or to actually allow skin authors to supply a texture for each part of the animation themselves. The latter seems the most logical, but meh.

Edit: I'll probably do something similar with the AutoCast layer. If only the Cooldowns were the same type of animation. /sigh

ButtonFacade doesn't handle the border (the overlay for equipped items, etc) anymore. That's handled by the add-on. AutoBar is outdated and SBF doesn't hasn't been adjusted for the change, yet.

The latest revision adds a few features for skin authors to tweak their skins a bit more.

Text layers now accept the following attributes:

• Font
• FontSize
• JustifyH
• JustifyV

Those respective attributes will default to their original values if the value is not specified in the skin.

As an example, the text justification for each layer is now how it's defined by the default UI if not specified by the skin. The same is now also true of the position of those elements. This helps fix some issues but I imagine it'll cause a few new ones. We'll see.

Keep in mind that skins that aren't updated will have some oddly placed text until they're fixed, but I want to make sure it doesn't interfere with anything before I let it pass. If you want to test it out, you can check out the latest alpha of Apathy, as it's been updated to reflect those changes or simply use one of the default skins.

No, you don't gave to use Ace3. But you do have to make sure that you're doing everything correctly. Some code would help.

Quote from Luzzifus

Then on Player login that:

if not nivBuffs_BF then nivBuffs_BF = {} end
bfButtons = LBF:Group("nivBuffs", "auras")
bfButtons:Skin(nivBuffs_BF.skinID, nivBuffs_BF.gloss, nivBuffs_BF.backdrop, nivBuffs_BF.colors)
LBF:RegisterSkinCallback("nivBuffs", self.BFSkinCallBack, self)

You have to register the callback before creating the group and/or skinning it.

In regards to the text layer changes, there were some issues that could not be resolved outside of leaving the alignment of the text layers where they were by default.

The changes make it so that skin authors can place the text anywhere, assuming that the know how to use height, width, justify and offset correctly.

P.S.

The change log specifically states that some skins will look bad until they've been updated to reflect those changes. Alphas are for testing purposes. If you're not going to read the change log to see what you're getting into, don't install them. Once they've been tested and I'm certain everything will go smoothly, I'll notify skin authors of the upcoming changes so that they can update their skins accordingly, prior to release.

On second thought, I'm going to leave some "old" code in for those skin authors who have a bit of a delay getting their skins updated. I'll probably remove this old code sometime after Cataclysm. But for authors who want to use and support the new features, you'll have to add a new key your skin table that will tell LBF that it's compatible with the new features. I haven't implemented it yet, but when I do, I'll let you know via the change log.

With the latest revision, the skin has to have the LBF_Version set to 40000 in order to use the new text attributes. Older skins without it will function as they previously did.

Example:

LBF:AddSkin("Skin Name",{
    LBF_Version = 40000,
    Backdrop = {
    ...
    },
    ... etc
}