Default aura help

[Stusteh]

I was trying out oUF_Faith and decided I wanted the player auras on the frame instead of somewhere else. To do this i just copied the code for the target auras and placed it in with the player code... The problem is it didn't get rid of blizzards default aura frames.

		self.Buffs = CreateFrame('Frame', nil, self)
		self.Buffs:SetPoint('LEFT', self, 'LEFT', -22, -0)
		self.Buffs:SetHeight(20 * 2)
		self.Buffs:SetWidth(240)
		self.Buffs.num = 11
		self.Buffs.size = 19
		self.Buffs.spacing = 2
		self.Buffs.initialAnchor = 'LEFT'
		self.Buffs['growth-x'] = 'LEFT'
		self.Buffs['growth-y'] = 'DOWN'

		self.Debuffs = CreateFrame('Frame', nil, self)
		self.Debuffs:SetPoint('BOTTOM', self, 'BOTTOM', 106, -33)
		self.Debuffs:SetHeight(20 * 2)
		self.Debuffs:SetWidth(240)
		self.Debuffs.num = 5
		self.Debuffs.size = 30
		self.Debuffs.spacing = 2
		self.Debuffs.initialAnchor = 'BOTTOM'
		self.Debuffs['growth-x'] = 'LEFT'
		self.Debuffs['growth-y'] = 'DOWN'
		self.Debuffs.onlyShowPlayer = True

[Mischback]

I guess you mean the buffs in the top right corner?

		local BlizzFrame = _G['BuffFrame']					-- get the default Blizzard BuffFrame
		BlizzFrame:UnregisterEvent('UNIT_AURA')				-- Unregister the event
		BlizzFrame:Hide()									-- hide the default Blizzard BuffFrame

		BlizzFrame = _G['TemporaryEnchantFrame']
		BlizzFrame:Hide()
		BlizzFrame:SetScript('OnUpdate', nil)

[Stusteh]

Do i just throw that in above it? I really don't know what i am doing.


EDIT: nvm thanks a ton

[Stusteh]

Ahh one more question. I forgot to throw the temp enchant frame on there. Is there a quick fix for that?

[Ferous]

BlizzFrame:Hide()

Question for you Mishback, or anyone else, why use

BlizzFrame:UnregisterEvent('UNIT_AURA')

? I'm just curious, because the BlizzFrame:Hide() works alone, does it create memory problems?

[Mischback]

Blizzard registered its buff-frame to this event to catch all the buffs/debuffs-stuff going on.
With this event the default-Blizzard-code is triggered. But since we're hiding the Blizzard-frame anyway, why we should keep the stuff runniing in background? So I unregister the event, which results in Blizzard's code NOT being triggered, so less CPU cycles are used on this.

[Ferous]

Originally Posted by Mischback Blizzard registered its buff-frame to this event to catch all the buffs/debuffs-stuff going on. With this event the default-Blizzard-code is triggered. But since we're hiding the Blizzard-frame anyway, why we should keep the stuff runniing in background? So I unregister the event, which results in Blizzard's code NOT being triggered, so less CPU cycles are used on this.

Okay cool, thanks Mischback. I was merely curious

So I want to unregister the weapon enchant event as well

[Mischback]

There is no weapon enchant-event...
Have a look nto the FrameXML-code. TempEnchants are checked with an OnUpdate-function. This is the script I set to 'nil' in my code-snippet.

[p3lim]

Originally Posted by Mischback This is the script I set to 'nil' in my code-snippet.

Hiding a frame with an OnUpdate script on it will pause/stop the script.

[Mischback]

Originally Posted by p3lim Hiding a frame with an OnUpdate script on it will pause/stop the script.

Oh, nice... Wasn't aware of that... Thanks! You never run out of things to learn!

[Taroven]

Originally Posted by Mischback There is no weapon enchant-event... Have a look nto the FrameXML-code. TempEnchants are checked with an OnUpdate-function. This is the script I set to 'nil' in my code-snippet.

Little late here, but hey, I'm bored. I always thought it was odd how they did that.

Random somewhat-related-but-irrelevant-in-context info about the bolded quote:

UNIT_INVENTORY_CHANGED is fired when temporary enchants are applied, removed, or altered. However, there's a caveat: Immediately on a fresh enchant or refresh, GetWeaponEnchantInfo() will return whether or not a weapon is enchanted - but it usually won't provide an accurate expiration time (mostly zero, sometimes the previous enchant duration on a refresh, and very rarely the correct time).

So if you're looking for enchant info with an accurate duration, call GetWeaponEnchantInfo() immediately on UNIT_INVENTORY_CHANGED, and if enchant info is found check it again about a second later via OnUpdate for the expiration time. It's a bit clunky, but also completely accurate and saves a few cycles when enchants aren't present.