Also, anybody knows a way to change the colors of the health bars? I only found the option "color health bar by class" which is fine, but since I have a mild form of colour-blindness I tend to have troubles telling some classes apart (mainly hunter and warrior, partially warlock and mage too), so I wanted to increase the colourcontrast of a few classes, or just completely change the colour.
I need certain buff to show on grid no matter who cast them, but I also need to be able to tell which one is mine and which has been cast by another.
Unfortunately that isn't something Grid is able to do right now. You might look at some of the HoT-related plugins to see if any of them support adding other auras, as several of them do exactly what you describe for HoT buffs.
I wanted to increase the colourcontrast of a few classes, or just completely change the colour.
It looks like you've already found the option to change colors in Grid, but I will shamelessly point you toward my addon Class Colors, which will allow you to safely change class colors for your whole UI. ;)
I have a problem with the pet bar in Grid. It's usually related to being mounted and entering combat. This does cause the Grid pet frame to become unsynchronized -- my other custom frame pitbull4 does not get affected and properly displays the health changes.
Dismissing and resummoning my pet usually does enable the pet frame again. I am wondering what pitbull4 does different from Grid since both must be using secure header frames.
Is there any way to move the central icon? For my purposes, seeing the debuff icon and quickly recognizing it, as well as being able to identify the player name is more important than knowing if they're at 100% health or 75% health. I would like to move the icon to the right side of the frame where I can make it larger and still keep 5 or 6 letters of player name visible.
No, but you could use a plugin like GridIndicatorCornerIcons, and assign everything you currently assign to the center icon, to another icon. Alternatively, you could try using another indicator for dispellable debuffs; personally I find that it's much quicker and easier to recognize a color on the border indicator than one of the hundreds of possible icons for debuffs. I only use the center icon for statuses so critical that they require an immediate response that doesn't depend on who they are on (like Frost Blast or Incinerate Flesh).
Since I'm playing a warlock, I'm rarely dispelling (yogg possibly). I'm more concerned about things like Acidmaw and Dreadscale debuffs that require me to know which player I need to move toward, rather than which frame I need to click on.
Some time ago I noticed frequent freezes during AV battlegrounds. I found the cause to be Grid : once I disabled it (and only it), everything went fine again. After chatting with some people on #wowace about this, it seemed it was caused by the SecureFrames itselves when PARTY_MEMBERS_CHANGED and UNIT_NAME_UPDATE events are fired.
Following their advice, I added a line to unregister UNIT_NAME_UPDATE at the end of GridLayoutHeaderClass.prototype:CreateFrames method (in GridLayout.lua). This prevents lots of freezes to actually happen (as UNU is fired every time a raid pet appear/disappear, or if someone is using a f*ing title rotation addon).
I thought you might want to know this, though I'm not sure what are the implication of unregistering UNIT_NAME_UPDATE from the secure frame.
Edit: according to Shefki (co-author on PB3 and PB4), unregistering UNIT_NAME_UPDATE does not have any drawbacks in 99% of cases.
[...]I finally tracked this down because today in my raid someone was running a title rotating addon which trips a UNIT_NAME_UPDATE event and forces all the group headers to update. They were rotating their title once a second so the whole raid I had the pet frames flashing. After the raid I went to try and fix this and couldn't replicate it anymore. I remembered the discussion about the title rotating addon and connected the two.
Which leads me to my other commentary. I'd strongly suggest that you discourage your friends from using these title rotating addons. I'm sure they're very cool but they create load on the entire game and on other players systems from the UNIT_NAME_UPDATE events.[...]
Especially in raid groups. Every time you change your title you trigger a UNIT_NAME_UPDATE event. This triggers an update of all the group headers because they blindly listen to that event and don't check the unit arg of the event to see if it's even a unit they care about. If the person doing this is in your raid and in the same party in the raid that you are you'll actually see two UNIT_NAME_UPDATE events for that player.
I've seen people running these addons in raids with the rotation time set as low as 1 second. This means you can be seeing 2 UNIT_NAME_UPDATE events per person doing this per second.
This is a horrible CPU churn. It's needlessly using CPU time of every single player in your group constantly.
I'd encourage players to stop using these addons at least in groups and/or in combat. Authors of such addons to reconsider distributing them or at least limiting their function outside of groups and/or combat. Baring a reasonable reaction from the community potentially Blizzard restricting the SetCurrentTitle() function.
Actually I ran tests during about an hour in AV using an addon to display the full UNIT_NAME_UPDATE parameters. I did not see any UNIT_NAME_UPDATE for "raidX" (i.e. player) but lots of them for "raidpetX". Basically an UNIT_NAME_UPDATE is fired every time a pet appears or disappears, which happens a lot considering you very often mount/dismount/die...
[2009/09/02 18:08:19-4468-x1]: AceConfigDialog-3.0-36:1797: Grid2 isn't registed with AceConfigRegistry, unable to open config
AceConfigDialog-3.0-36:1730: in function `Open'
AceConfigDialog-3.0-36:1797: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1795>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher":9: in function <[string "safecall Dispatcher"]:5>
(tail call): ?:
AceGUI-3.0-25 (Ace3):305: in function `Fire'
...AceGUI-3.0\widgets\AceGUIWidget-BlizOptionsGroup.lua:67: in function <...AceGUI-3.0\widgets\AceGUIWidget-BlizOptionsGroup.lua:66>:
(tail call): ?:
<in C code>: in function `Show'
Interface\FrameXML\InterfaceOptionsFrame.lua:28: in function `InterfaceOptionsList_DisplayPanel':
Interface\FrameXML\InterfaceOptionsFrame.lua:46: in function `InterfaceOptionsListButton_OnClick':
<string>:"*:OnClick":2: in function <[string "*:OnClick"]:1>
I recently updated to the latest version of Grid. Unfortunately, my buffs were gone. I tried adding them but I do not see an option for single target and group, i.e. Prayer of Fortitude and Power Word: Fortitude. When I added both as single entries, a missing buff icon would show even though I had either one. Did the latest update mess with auras? Please help! Thanks!
The only recent change to the aura system was a bugfix to ensure that debuffs with the same name as their debuff type (i.e. there is a debuff called "Poison", with a debuff type of "Poison) are correctly classified with their debuff type. This change should not affect any other auras, and I haven't experienced any problems.
However, from your post I'm guessing that you previously had the plugin GridStatusMissingBuffs, and somehow deleted or disabled it. Grid itself does not, and never has, included any features to combine or otherwise associate single target and group buffs with each other. GridStatusMissingBuffs does exactly that.
I have a question regarding the status "Unit Health".
My guild is slowly starting to get to Anub'arak hardmode p3 and my usual approach of only displaying health deficit is a bit subpar there.
Now my problem: "Unit Health" is doing exaclty the same as "Health Deficit" for me (except for the health threshold).
All I want is a numerical display of the current health.
I've been using Grid with Fubar for years and adjusting my config by using the drop down menu config (right click iirc) through the Fubar plugin. Recently (possibly just the most recent release, I'm not sure) the drop down config menu stopped working so the only way to config was through the normal /grid config or by left clicking the Fubar plugin. I am switching away from Fubar and going to a LDB and had hoped that the change I was seeing was due to Grid changing to a LDB plugin and removing the Fubar plugin, but it performs the same.
Was the removal of the drop down config menu an intended change? If not, is there an ETA on when that will be added back in?
Will an LDB plug in be added to grid at some point?