I said this in the recount thread already but let me be more blunt:
Don't LoD Recount. Recount already allows content and group based collection filters. Recount's idle CPU load is practically nil and it won't accumulate any data in that case. If base footprint of Recount is a concern for you outside raiding I cannot see how you could viable use Recount when raiding.
Just start using Recount's collection filtering and you should be set, that's why it's there in the first place.
Ok, well the only modification was making the mod Load on Demand in the toc file (Recount) file. Otherwise it's the exact same as what the author provided. In either case, I'm not trying to antagonize anyone here. I was just wondering if anyone knew anything about a possible solution here. If it's bothering anyone then let the issue go and no hard feelings.
The main reason I made Recount LoD was because I was getting unreasonable slow downs on logging out on one of my toons when Recount was loaded. Beyond that, I just didn't need all the overhead of using the mod in BGs/Arena where every millisecond of latency makes a difference. I realize it's a small difference, and again, if what I said bothers you then don't take offense because I mean none.
Thank you for all the suggestions Phanx and keep up the good work on your respective addons both of you. Thank you for making and updating them.
You could put everyone in one row (or a row of more than 5) but you would have to sacrifice some control over how they're sorted, and you couldn't get the space between them. You'd also need to define your own layout in Lua.
No, but if you look at GridLayoutLayouts.lua it should be fairly self-explanatory. It's just the Blizzard secure header attributes + a Grid-specific "isPet" attribute to define pet groups. These attributes are briefly documented in GridLayoutLayouts.lua, and very well documented in one of Blizzard's Lua files (I forget which one).
The aggro status (I'm using the "border" as the indicator) seems to be getting stuck since I've upgraded to 3.1. People pull aggro, but then it never resets after the party exits combat. I'm even seeing it when I'm solo.
I've upgraded to version 1174 on wow.ace.com/projects/grid but it didn't seem to fix it.
Edit: I take it back -- it works much better when you actually unzip the files into the addon folder. =/ Sorry for the false alarm.
Odd, I have aggro set to the same indicator as you, and was getting the same issue on the PTR, but it seemed resolve itself for me with the update to r1174.
Admittedly, that was week or so ago, so I guess it's possible Blizzard might have changed something in the meantime that has broken it again. I'll be raiding tonight, so I'll be sure to report back on whether I have that problem back too.
Well it seemed fine to me tonight, even if the actual raid instance itself was laggy as hell, which made the updates kind of slow, but I'm certainly not getting the error reported in the last few posts anyway.
I'm really not sure what's going on then, sorry.
<edit> oh right dfscott, you seem to have the problem fixed then? Good. :)
Truffleshuffle, try the latest version which was linked on the previous page if you haven't already.
Anyone having issues with the icon timers not working in the newest version? Had the problem with the previous version as well so I was using one from December which works fine. Any help would be appreciated. I've toggled the option on and off etc... If I go back to the older version I was using it works fine.
edit: got it working.... had to turn the show duration on for each buff/debuff apparently