Read Me First

Changes 1.406

Flexbar Development Under New Management: With the apparent disappearance of Dhargo, Flexbar is now being worked on by a new development team, under the direction of Dagar. We are all avid users of Flexbar and are dedicated to keeping it the most essential WoW UI mod around. Dhargo created an amazing tool for all of us, and we can only strive to live up to the standards of his creation. Version 1.406 is primarily a bug fix release, but we managed to squeeze in a few enhancements while we were at it.

New Text3: Another text field for your buttons, Text3 is located on the center of the button. New command /Flexbar Text3 added, the syntax is the same as the other text commands.

Key Binding "Toggle Button Info": A new keybinding has been added, pressing this key will toggle between your text settings and showing Button number, ID mapping, and Group membership, on the button. This button will not disrupt your Text1-Text3 settings. While active, Text1 shows the Button Number, Text2 shows the Group Number the button is a member of, Text3 shows the ID the button is mapped to.

Duel targets are 'hostile': Flexbar will now consider your target in a duel to be 'hostile'. This is more in line with user expectations.

On='trackingchanged' Event Added: Target= any one of the following: herbs, minerals, treasure, beasts, humanoids, hidden, elementals, undead, demons, giants, dragonkin, senseundead, sensedemons or none. 'none' will fire if we loose tracking

Several Major and minor bug fixes: Many bugs were squished for this release, including the very annoying "Wandering buttons" bug. Eforts have been made to make special attack 'dodge' work correctly in conditions. Flexbar's handleing of clicks on buttons useing FlexPet, has been made more like Blizzard's. Non-visible creatures when should be handled properly when determining creature type. Fixed nil string concatenation errors in lines 409 and 433. The 'scaled<>' condition should now work properly.

Changes from 1.36 to 1.37

Introduction: I realize it's a pain when I change structural details in FlexBar and you have to change your setups. I give a lot of thought to these things before doing it. Please remember I still consider FlexBar to be Alpha Software. Until I am satisfied with the feature set (not until pet buttons at least) and satisfied with a low enough number of known issues will I move it to beta status. Once I do that I will be even more reluctant to change things like these. Until then, these changes were necessary to allow me to keep extending it without working around poor design decisions made early on.

Buttons Above 72: Prior to this, there were 96 buttons, and the buttons above 72 did NOT have a 1-1 mapping of default ID to button number the way buttons 1-72 did. In order to fix this, I have increased the number of buttons to 120 and now there is a 1-1 mapping of default ID to button #. That means that, before you remap anything, button 73 has ID 73, button 88 has ID 88 and so on.

What this means for prior users - The apparent location of your abilities on buttons 73-96 will move. Abilities that were on 85-96 will now be on 109-120. For all but warriors and druids, abilities that were on 73-84 will now be on 97-108. If you had abilities on these buttons and you were just remapping to them, then no change needs to be made as they are still at the same ID. If you were displaying those buttons and not remapping to them, just display the new buttons, drag the abilities to the old buttons and you're done. Finally if you were both displaying those buttons and remapping to those ID's - you will have to move the abilities back to the old buttons, and change and remapping commands to reference the new ID's.

SetTexture: SetTexture used to set the texture by button #. This has changed to setting the texture by ID #. This is to facilitate the new features flexmacro/flexscript/autoitems. While you can still set on events - this ability is mainly for flex-actions (and later pet buttons).

/wait command: Has been changed to /fbwait to avoid replacing /wait voice emote.

Extending FlexBar: The way you hook into WoW events has changed - please read that section.

IsUsable: While this isn't my change, it warrants a word. In interface version 1.4 of WoW, Blizzard change the return value of IsUsableAction. Originally it only indicated that a prerequisite event had happened, (dodge for overpower, parry for riposte etc.). Now it indicates that : A prerequisite event has happened, you are in the correct stance, you have enough mana/rage/energy and it is out of cooldown. If you are a stance dancing warrior who used macros that changed to battle-stance (if you weren't in it) then cast overpower (on the next press) and were used to using isusable to light up/show your buttons when you were not in the correct stance, this will no longer work.

For now, use the new On='TargetCombat' Target='Dodge' to capture this and use a timer to hide the button and an On='CooldownStart' to hide it.

This isn't the definitive answer, but it is the best I have atm I'm afraid.