/cancelaura

[zork]

See post three...disabling is possible via SecureAuraHeaderTemplate

[Xrystal]

I just use one cancel aura macro and just add the buffs I want removed in the list. It will just go down the list and remove whatever is active. Whether it is one at a time I don't know but it will at least cut down the number of macros while this gets programatically resolved.

[zork]

Hmm bBuffBars says that this is working with the SecureAuraHeaders...hmm

http://www.wowinterface.com/download...Bars.html#info
http://www.wowinterface.com/download...-nivBuffs.html

Siggs post
http://www.wowinterface.com/forums/s...143#post213143

To sum this, when using SecureAuraHeaderTemplate for buffs/debuffs and buttons via SecureActionButtonTemplate it is possible to make it secure.

[yj589794]

Originally Posted by zork To sum this, when using SecureAuraHeaderTemplate for buffs/debuffs and buttons via SecureActionButtonTemplate it is possible to make it secure.

This has been known about for quite a while. The problem is that for oUF the auras element is the most complicated one, and to re-write it to support SecureAuraHeaderTemplate is not an easy job.

It will also mean that a lot of the existing aura functionality will be reduced / removed.

[zork]

Yeah, not sure if that is needed really since we could easily use a self-created buff/debuff mod just for player auras. I had this for years.

[neverg]

Originally Posted by zork Yeah, not sure if that is needed really since we could easily use a self-created buff/debuff mod just for player auras. I had this for years.

Agree. Think it's best to keep the functionality as it is than to remove features just to support player Auras Right Clicking. Like zork said, one can use an addon for that. Speaking of which...zork have you re-written rBuffs with SecureAuraHeaders in mind?

[zork]

Yes I do. But this will will delay Roth UI because I just can't copy cast any already existing code. Gonna read into that topic first. :/

[zork]

Well...hmm I actually just had an idea and it worked...sort of.

I can track which buttons are my player buff buttons, so only for them I add this call:

      button:SetScript("OnMouseUp", function(s) 
        if s.filter == "HELPFUL" then
          local buffname = UnitAura("player", s:GetID(), s.filter)
          local eb = LAST_ACTIVE_CHAT_EDIT_BOX
          if eb then
            eb:SetText("/cancelaura "..buffname)
            eb:SetFocus()
            eb:HighlightText()
          end          
        end        
      end)

Now what happens here is: I extract the BuffID, get the Buffname and print a string to the last active chat editbox. I set the Focus and Hightlight the text.

Now what is reallly strange is the follow: Just hittting Return does not work...I thought (WTF!!!)
If I copy the string into clipboard, paste it right away and hit Return it works.

So combination is now for me: RightClick buff you want to dispell + SHIFT-C -> SHIFT-V -> RETURN

Can anyone tell me why the exact same string will only work once copied from clipboard?

I don't understand that to be honest.

[Dawn]

I was expecting this to be part of oUF at some point, won't it?

[yj589794]

It will be as Haste has an issue tracker on GitHub for this feature. Due to the complexity of rewriting the auras element, it will probably take a while.

[MoonWitch]

Thanks for posting this though. I had been trying with the secure button template, but I assume that was indeed wrong :P

[haste]

I made a slightly lengthy post about my plans for the secure aura header, but Opera Mobile felt that I shouldn't post it. So here's a quick flow of what I'm planning to do:
1) Write up a new element to do player auras and make it resemble the current one as closely as I can
2) Compare the difference between the two (both logical and function wise) and see how sane it would be to merge the two elements into one.
3) ???
4) Profit

I also have some changes I want to make to the default aura element before I start with this, but those are pretty minor.

(sent from my phone)