Support for the XP and Reputation Bar, Bartender4 hides them so it can show them again. Disabled by default.
Note: The XP Bar hides itself when you reach max-level, and the Reputation Bar hides itself if you are not tracking any reputation.
The Possess Bar usually only uses 10 buttons to the limit of 10 buttons on the pet bar, that leaves button 11 and 12 empty. Button 12 (id 132) is now being used for a Leave Vehicle button to be able to leave vehicles properly.
Without a full 12-Button Main Bar, you probably want to Macro /script VehicleExit();
I may add another form of button for this at some point, but not right now.
The MicroMenu can once again be vertical again, however it does not have a full-blown Rows configuration like the actionbars do, due to some issues with the non-square micromenu buttons.
As a result of that, padding between the buttons is currently not available either.
Its planned to make the MicroMenu use the default ButtonBar template too in the future.
You can now enter any macro conditions into an editbox in the Config GUI which will feed the state driver. The syntax is not validated, so its your own responsibility to know how macro syntax works!
Example:
[form:1]9;0 -- Page to Bar 9 in Form 1, otherwise don't page at all (id 0)
The new "type" attribute allows the state header to use any macro conditions to be used for paging, currently only used in Warlocks Metamorphosis which only reacts on "stance" and not on "bonusbar" in build 8982.
If type is not set, it defaults to "bonusbar" for compat reasons.
Metamorphosis is on slot 1 for GetShapeshiftFormInfo(), but when active GetShapeshiftForm() returns 2.
Added a hopefully temporary hack to work around the issue.
Bindings reported will always be in the format "Pet Button 1 (action_name)" now.
Note that bindings are always directly to the button, no matter whcih action is
currently associated to it, not as [1] claims.
[1]: http://jira.wowace.com/browse/BT-39
Apparently the cache for the click-frames taints its first element after frame creation, so a one-time call of GetClickFrame() after frame-creation removes that tainted element from the cache, and all future calls return the proper secure frame. [1]
[1]: http://forums.worldofwarcraft.com/thread.html?topicId=3773503744&sid=1&pageNo=4#60
Hendrik Leppkes