Originally Posted by dafft
|
a quick tutorial on the main issue(s).
not familiar with the specific features of this addon, but the main thing between WoW 4.0 and 4.1 was that the nameplate "assembly" changed. if you go back to WoW 3.X versus WoW 4.1, you also have to include the way Blizzard controls nameplate "overlap" (i don't know if NameplateModifier does anything with that; my guess is that it does not).
that means that all the liitle UI widgets that comprise a nameplate changed in organization. nameplates contain a variety of elements, including a bunch of texture/text regions, and two "children": health bar and cast bar.
the change that occurred relates specifically to the cast bar: several texture elements that were logically associated with the cast bar but (historically) associated with the nameplate proper moved, physically, from the nameplate proper to the cast bar itself.
this changed the manifest of return values from the
Frame:GetRegions() API call that every nameplate addon has to do to identify various nameplate elements for reskinning. if this manifest changes, it generally results in major addon breakage.
for WoW 4.1, Aloft's code looks roughly like this:
Code:
local nativeGlowRegion, overlayRegion, highlightRegion, nameTextRegion, levelTextRegion, bossIconRegion, raidIconRegion, stateIconRegion = nameplateFrame:GetRegions()
local healthBar, castBar = nameplateFrame:GetChildren()
local castBarRegion, castBarOverlayRegion, castBarShieldRegion, spellIconRegion = castBar:GetRegions()
(the healthBar is nothing "special", just a standard StatusBar... a Blizzard API widget, documented
here, along with everything else; in WoW 4.1, the castBar has become more complicated.)
ultimately, there will be some code like this somewhere in NameplateModifier. it may be as simple as just updating the code in place to reflect the new organization.
hope that helps.