Firstly, thanks for AltAura! It's a great module. One very minor thing I have noticed (hunter) is that a when a target is wing-clipped AND in a frost trap's aura, that the wing-clip de-buff is over written by the frost trap de-buff. I don't have ANY filtering enabled, and this is the only time I see this.
I get a ton of issues while raiding with target frame buffs overwriting other buffs or showing the wrong cooldowns. I should probably clear out my AltAura-related savedvariables. I'm not using any filtering on the target frame.
It seems that AltAura plays fast-and-loose with debuffs. I've noticed that Hunter's Mark will often have a red border for a few seconds then change to a blue border to reflect that it is a Magic debuff. Even worse, it sometimes has the wrong icon (yesterday I couldn't see it because it had the Shadow Word: Pain icon).
Clean installation of Pitbull/PB_AA didnt gave that option. Infact i couldnt do it since the first release. The only way i can place them without split to bottom or top is to load original Aura module and choose side there,then relog with AltAura. I think it has something to do with taking side from the original Aura settings.
This seems to be my experience as well. It apparently imported the side settings from the regular Aura module and then I couldn't see any way to modify them with AltAura.
Update: Settings of side are located in global section of each frame's layout,not in the module section of AltAura. auraSide,debuffSide,buffSide. Maybe it has something to do with this.
That could be what's going on. I know I was looking under Other->AltAura or something for each frame because that's the intuitive location.
If it helps any, it's the mouseover frame that I'm trying to mess with.
So it's maddening that I can't choose which side to put my auras on without splitting them, especially since it's sort of using the settings that I chose in Pitbull_Aura. I also don't understand why some frames have an aura frame size (whatever that is) and some don't (mouseover versus player pet frame for example).
I've had a quick look over... what are the key differences between this implementation and the default pitbull one, besides the obvious configuration differences?
I recently added weapon buffs to the standard pitbull aura; you might want to merge that into your implementation too.
The difference is that the layout of the buff and debuff icons is done only when needed.
There are probably a few bugs, but otherwise it should be working exactly as the original version feature-wise. I may add features, but my idea behind this is the same as the patch I provided for PitBull_Aura, except it's provided as a module so it can be activated and de-activated at runtime.
Is this supposed to be run with Pitbull_Aura active?
Tried running this with Pitbill_Aura disabled and got an error:
[2007/09/04 18:03:30-1763-x11]: PitBull_AltAura\layout.lua:38: AceModuleCore-2.0: Cannot find module "Aura".
PitBull-r47902\PitBull.lua:3735: in function <Interface\AddOns\PitBull\PitBull.lua:3722>
<in C code>: ?
AceEvent-2.0-44693 (Ace2):363: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:341>
Am I supposed to run with Aura enabled then? /confused
Edit: I'm thinking maybe I need to run at least once with both to import settings or something?
I have reworked my patch to make it a standalone module of PitBull. It is now available under the name "PitBull_AltAura". The patch has been reworked quite a bit and is much less buggy.
I'm going on vacation starting tomorrow, so I won't be able to fix bugs for a week.
Please test and report here what your experience is.
I'm interested in this project, but before I try it for myself I'm wondering what your overall goals with it are. Also, I know a lot of people cite Pitbull's Aura module as a source of performance issues, so many people are probably going to look to AltAura to possibly attempt to address this.