Authors CurseForge

Doesn't seem to be fixed, just ran the updater and still had to go back and edit main.lua to fix that typo.

I'm getting this..."error" (in my chat frame, doesn't actually show up in BugSack) when I try to use UAB to bind Remove Lesser Curse to my middle mouse button on the party/raid frames and copied to all other frames. Note: I have ag_UF and Grid installed, no other unit frames. Picture of "error" attached at bottom of post.

Just to be sure, could you check to make sure it is version "2007-03-26 (31043)" (r31043). I've seen this error before, but not recently. I'm using the same frame add-ons (aguf and grid) but not seeing this error.

The error reported yesterday would only show up in-game for frames that were not supported by a uab plug-in (the default frame support).

If you are sure you have that latest revision, could you post your saved variables file? I can try to use it, and see if I encounter the same issue.

I think I found out what the problem is. The frame names in the aUF framegroup are not matching the frames that aUF is creating. At least for raid groups and party pets. Not sure if aUF changed the frame names, or if UAB has been wrong in this respect all along. I'll take a look to get the correct names, and post an update.

r31269 (3-29-2007) has the aguf fix, and another update to resolve an issue that occurred if you have both regular and hostile actions for a slot in an action set, and you remove either the regular or hostile action for that slot.

For the time being, both the old aguf frame names and the new aguf frame names work according to the settings for the aguf framegroup.

Along the same vein, here's the "error" I get when I try to add someone to MainAssist. http://www.wowace.com/files/MainAssist/

This occurs when I am clicking on either an ag_UF frame or a PitBull frame (giving PitBull a try today) and adding them as a custom assist via keybinding.

edit: This may not be a UAB error, not really sure.

Those are not errors. That is the message that UAB gives when it finds a unit frame that has no supported frame group. It is telling you that it has no frame group, and it is using the default settings for the specified frame.

To get rid of those messages, I would need to add a UAB plug-in for MainAssist.

Working on a uab plugin for MainAssist and PitBull. For the time being "default" support should work just fine. You just will be unable to set the display characteristics specifically for the PitBull/MainAssist frames (it will use the default settings).

Should have these plugins uploaded soon.

plugin for PitBull now available (uab_PitBullFrames)

Haven't posted in a while, and haven't changed too much in the meantime. I've improved the PitBull support a bit, though, and there are some changes in the works.

1. mutliple activators referencing same set of actions

2. key-activators (haven't fully worked this one out yet)

3. make the appearance modifiers extendable through plug-ins (highlight border, low alpha, etc. - allow additions to this set)

4. customizable buffs/debuffs (allow you to add/remove buffs/debuffs)

5. status plug-ins returning a cooldown count along with an active status (This will come after the 2.1 update. The cooldown information will be used as the cooldown for the action button)

6. status plug-ins that check you (player) instead of the unit for the selected status (choice to check you instead of the target is per action, not on the status plug-in)

7. modified-click support on bar actions (UAB change) (support distinct actions for shift-click, alt-click, etc. on the action button - normally for different ranks, but not restricted to that)

Quote from Zuno »

4. customizable buffs/debuffs (allow you to add/remove buffs/debuffs)

5. status plug-ins returning a cooldown count along with an active status (This will come after the 2.1 update. The cooldown information will be used as the cooldown for the action button)

6. status plug-ins that check you (player) instead of the unit for the selected status (choice to check you instead of the target is per action, not on the status plug-in)

Updated to include support for these changes. All plug-ins updated as well.

Every time I try to drag a spell into uab's config, wow crashes, I've even disabled every addon *except* uab, and it still crashes.

I'm a having a very minor problem with "Direct Cast." On my Warlock, I have right-click bound to Fear for focus, but until I go into the FuBar menu and manually toggle "Direct Cast" off and back on, I get a single button menu when I right-click my focus unitframe (I'm using Pitbull & uab_Pitbull).

Quote from PetiteMort »

I'm a having a very minor problem with "Direct Cast." On my Warlock, I have right-click bound to Fear for focus, but until I go into the FuBar menu and manually toggle "Direct Cast" off and back on, I get a single button menu when I right-click my focus unitframe (I'm using Pitbull & uab_Pitbull).

I posted about a PitBull + UAB issue yesterday in the PitBull forum. PitBull reorganizes the parent/child associations whenever the group/raid makeup changes. This was causing some problems with UAB. I posted an update today that I believe resolves this problem.

Along with this update, I merged all the plug-ins (uab_* mods) into the main UnitActionBars add-on, so UnitActionBars is not a package as WowAceUpdater sees it. If you use WowAceUpdater, these plug-ins will be broken out into separate mods when downloading UAB the next time. If you download UAB explicitly, they will now be loaded inside UAB. None of them take up much memory, and they don't conflict with one another.

Let me know if the problem you have been seeing is resolved with this version (r42813)

Hey Z,

On login I'm getting uab_oRA2Frames.lua:1: AceModuleCore-2.0: The module "oRA2" has already been registered in a warning box. Uab seems to run fine.

Try removing all UAB related add-ons, then downloading UAB from the files.wowace.com site, or using WowAceUpdater to download UnitActionBars. All the extra plug-ins are now part of the main add-on and get expanded by WAU when it installs the add-on.

Very basic problem: When I join AV, my computer locks up. Without UAB running, no problem.

I'm using Grid for raidframes, Pitbull for party frames (which disables in raids).

Am I missing something obvious here?

I'll take a look. I've noticed lag as well, but another person told me they took off grid in that same situation and the problem went away. I'll take a look to see what might be causing it in uab.

On further review, it comes up anytime I'm in a raid, so it seems very likely that it's Grid-related.

Really excellent add-on otherwise.

Although there may be issues with Grid, I did find a lag problem that UAB may be causing. A couple discussions last night pointed to UAB as a likely culprit as well. Some of my guild members had encountered similar crashing/significant fps lag when they had UAB loaded and the makeup of the raid was changing (add/remove player, player comes online/alive, and other times).

I recently had to hook SecureGroupHeader_Update to handle PitBull changing unit frame parent/child associations when raid makeup changes (happens at some odd times). The re-parenting was causing UAB to not work on several frames, hence I needed to fixup the UAB-to-unitframe associations to match post-PitBull reassociation.

I found a place where I was doing way too much work (and missed some work) whenever SecureGroupHeader_Update was called, and I've posted an update. This update significantly reduces what UAB does on the SecureGroupHeader_Update call, and should help. Let me know if you are still noticing the issue with this change.

Didn't do the trick-- still freezing when joining raids.