70 - Aura debuffs on enemies on same row as buffs
--What is the enhancement in mind? How should it look and feel?--
I want the same functionality as in PB3! There, if my enemy doesn't have any positive buffs, my debuffs will appear on the row just below his portrait. Otherwise, if the enemy has some positive buff, put my debuffs on the row beneath it.
--Please provide any additional information below.--
Because right now, PB4 will have my debuffs on a separate row, creating a gap between portrait and debuffs.
| User | When | Change |
|---|---|---|
| Shefki | Wed, 08 Apr 2009 22:22:41 | Changed assigned to from ckknight to Shefki |
| Shefki | Fri, 03 Apr 2009 21:25:26 | Changed assigned to from Shefki to ckknight |
| Shefki | Fri, 20 Mar 2009 11:06:01 | Changed component from None to Aura |
| shiin | Thu, 05 Mar 2009 08:35:54 | Changed status from Waiting to Replied |
| Shefki | Tue, 13 Jan 2009 10:23:54 | Changed priority from Medium to Low Changed status from New to Waiting |
| silkfire | Tue, 13 Jan 2009 07:52:03 | Create |
- 6 comments
- 6 comments
Facts
- Last updated on
- 09 Feb 2010
- Reported on
- 13 Jan 2009
- Status
- Replied - Someone has replied after waiting for more information.
- Type
- Enhancement - A change which is intended to better the project in some way
- Priority
- Low - Might slip to a later milestone.
- Component
- Aura
- #6
cerbul Tue, 17 Nov 2009 11:18:22I do agree that having buffs/debuffs in the same row is confusing. But when you have a situation when you need let's say both buffs and debuffs in the same zone of the frame (ie top of the bar), there is one good solution for this: make buffs + debuffs use every row, but pick first the ones chosen with a "check" to have priority over others (buffs/debuffs), and just modify the offset of display when the number of rows used by the one with priority changes. This will not leave any blank rows but in the same time will not put buffs/debuffs on the same row.
- #5
Kitjan Thu, 22 Oct 2009 18:09:08You can make a LUA Text to approximate this.
- #4
Tamitaz Sat, 19 Sep 2009 22:04:02(sorry for bad english ...) I don't think that Silkfire looking for is a combined layout that mixed buffs and debuffs. I think is much more a thing like in ticket 403.
The problem is if, for exemple, you place a row of buffs directly under the target's portrait, and a row of Debuffs under the row of Buff (using offset) then, when the target has no buff, there is a gap between the portrait and debuffs.
A solution for this may be : - make the offset of one depending dynamicaly of the other - add an option for switching buff and debuff position if the target is friendly or if it is hostile
- #3
tlundse Fri, 31 Jul 2009 21:32:15I would also like to see what Shiin asks for, an option to anchor the debuffs under the buffs, instead of under the unit frame. That way you can make both buffs and debufs occupy 100% of the unit frame width and save a lot of space.
- #2
shiin Thu, 05 Mar 2009 08:35:53Regarding this suggestion, I'd like to add a variant thereof: Having the debuffs attached right after the buffs or vice-versa would be a nice option when using only one aura row (but it would make a lot of sense when having multiple rows activated). The intended look-and-feel is the same as of the classic CastParty addon.
- #1
Shefki Tue, 13 Jan 2009 10:08:16If you're looking for the combined layout that basically mixed them I'm not inclined to implement it. There's several reasons for that.
It makes the layout code incredibly complicated.
It makes the new Border system confusing as all get out. Borders are not deterministic by if they are buff or debuffs anymore.
It was confusing as hell anyway. Buffs and debuffs were not deterministic.
It required layout options that made the layout options confusing. A major goal was implementing aura with a single set of options. Changing one option shouldn't change the entire set of options to something else.
I talked to a lot of people and they told me they didn't like this layout. So considering all of this I didn't think it was necessary.
I'll leave the ticket open for now. But at this point it's not a priority.