Authors CurseForge

LibActionButton-1.0 is a library to create and manage Action Buttons. And when i say action button, i don't necessarily mean buttons that are limited to the 120 actions the game gives you.

LibActionButton-1.0 implements a full replacement button which can either use the 120 actions provided by the game, or alternatively be completely independent of those actions, and directly use spells, items, macros, etc, letting the addon using LAB-1.0 manage the contents of the buttons.
Of course, actions and non-actions can also be mixed.

The whole button handling code, while roughly modeled after how Blizzard manages their buttons, has been cleaned up and optimized quite a lot. Replacing the whole default UIs action buttons with LAB-1.0 based buttons will increase your performance, even if not by much.

Features
- 100% support for Action-based buttons.
- 99%* support for non-action based buttons, containing spells, items, macros**.
- LibKeyBound-1.0 integration
- ButtonFacade support
- Configuration of the buttons through a config table
- Static Buttons (Disable Drag'n'Drop, so the user cannot change the contents of the button - only for non-action)

* 99% because Drag'N'Drop in combat is not 100% the same as for action buttons. You can drag a spell on the button, but only with a real drag (keep mouse button pressed from action pickup to action drop). Having the action on the cursor and clicking on the button to drop the action only works out of combat.

** Macros are not fully supported yet. You can drag them on buttons, and the macros will be cast when you click them, however alot of visual feedback is still missing.

ToDos
- Finish Macro support
- Pet Action support (replacing the pet bar)
- Add support for non-combat pets/mounts on the buttons
- New 4.0 "flyout" action support
- Extensive Testing

Maybes
- "Auto-Assist" option from Bartender

Requirements
- Requires WoW 4.0
- Its currently required to have a secure header driving the buttons.

Primarily aimed at replacing the custom Action Button code in Bartender4.5, i decided to make it a proper library, for everyone to benefit.

If anyone is creating secure buttons with custom actions on them right now, this could be potentially interesting for you. For example, this could be addons that provide bars for Hunter Aspects, Mage Portals, or something generic like AutoBar. Any kind of button that holds items or spells, and needs to behave like a typical Action Button, can make use of this library, and get rid of all the interfacing to the restricted environment and event handling.

Project: http://www.wowace.com/addons/libactionbutton-1-0/
API: http://www.wowace.com/addons/libactionbutton-1-0/pages/api/

If anyone is interested in using it, i would appreciate any feedback and features you might need/want.

LAB-1.0 is now being used by the Bartender4 Cataclysm branch, and should be fully functional for "action" based buttons.

I'll expand on the non-action functionality in the coming weeks, mostly as i need it in Bartender. ;)

You can't hook the Update function, its all in locals =p

LAB buttons does not use ActionButton_UpdateCount at all. It replaces most Blizzard functionality with its own. (Adding the early return just disables all count numbers, obviously)

Thats the price for the added flexibility i wanted. Addons working with Blizzard Action Bars will not work with Bartender anymore.

I don't know what would be calling AB_UC. LAB or BT4 certainly don't, and i don't use any of Blizzards initialization code on the buttons. Something funny must be going on!

I am working on adding a sane possibility to register callbacks for the common functions, so you get notified when they get called, and can do what you need to do.

I won't allow hooking, because that always has a high risk of blocking LAB to function, which happend so often before with BT4, that i would rather not see it happen again.

I'll probably go with a CallbackHandler interface, still trying to decide on the best way to handle this, which also works when the lib gets upgraded.

Ok, i implemented a set of callbacks and some new APIs:

[B]lib:GetAllButtons()[/B]
-- Returns a hash table containing all currently registered buttons as keys.
-- Like: {[button1] = true, [button2] = true, ...}

[b]lib.RegisterCallback(self, event, method, ...)[/b]
-- Register a callback handler. Default CallbackHandler-1.0 syntax
-- Example: LAB.RegisterCallback(MyAddon, "OnButtonCreated")

And all the events that fire callbacks
All callbacks receive the button as the first argument.

[b]"OnButtonCreated"[/b](button)
Fired when a new button was created

[b]"OnButtonContentsChanged"[/b](button, state, type ,value)
Fired when the type of the button changed due to a user action, drag'n'drop, etc. 
Currently not being used in Bartender4, and only relevant for the addon controlling
this button, and requiring to save the new contents. 
"OnButtonUpdate" will fire in addition to his, as a full button update will
run as well, so addons just needing to update their additional information on the button
do not have to use this at all.

[b]"OnButtonUpdate"[/b](button)
Fired when a full button update occurs. 
This is the equivalent to ActionButton_Update.

[b]"OnButtonState"[/b](button)
Fired when the buttons state changes (after a click, for example)
This is the equivalent to ActionButton_UpdateState.

[b]"OnButtonUsable"[/b](button)
Fired when the buttons usability changes. 
This is the equivalent to ActionButton_UpdateUsable.

Let me know if you need more information or more callbacks.
One thing, though: I will not fire a callback in OnUpdate for obvious reasons.

These changes are implemented in Bartender 4.4.13

This should possibly work

FlyoutButton_SetCursor(self.command, self.value, self.subValue)
local type, action = actBtn:GetAction()
if type == "action" then
  PlaceAction(action)
  actBtn:UpdateAction(true)
end
ClearCursor()

3rd party interaction isn't really all that well though out yet.
It works perfectly as a self-contained button, but isn't too friendly to anyone trying to hook into it.

I was linking for someone who might benefit on WoWInterface, when I noticed "error 404" for the API link on LAB's main page description. The API can be found by clicking Pages, but for some people, that's a bit too much creative thinking.

Just pointing it out in case you want to update the link, Nev.

The links work fine for me.

Hmmm, now it works for me as well. A Chrome issue, perhaps? Meh, doesn't matter; link works.

PSA: LibActionButton-1.0 now uses LibButtonGlow-1.0 for the spell activation alerts, due to a taint bug when using the Blizzard APIs (or even the Blizzard template).

If you use LibActionButton-1.0 in your project, you should include LibButtonGlow-1.0 as well, otherwise the glow effects will no longer show (it will however not error out).