Originally Posted by Xrystal
Yep, that is the other reason. I was thinking more the case that between the aura's being read and the timers being set that perhaps the aura at no 3 wasn't the same as the one initially at no 3. I'm not sure if things get shuffled around by wow based on expiration order.
|
They get shuffled around based on start time. Note refreshing an existing buff doesn't change its position.
Also, you should consider buffs getting reapplied before their timer expires or the user canceling buffs. Both of these make
C_Timer.After() a poor candidate.
Originally Posted by Fizzlemizz
Code:
button:SetScript("PostClick", function(self, arg1)
self:Hide()
end)
Code:
local function popup(self)
self:Show()
PlaySound(1221)
FlashClientIcon()
end
|
SecureActionButtonTemplate is a protected template, meaning you can't show or hide the button while in combat.