["Filter Abolished units"] = "Filtere freigegebene Einheiten",
["Skip units that have an active Abolish buff."] = "Auslassen von Einheiten, die einen aktiven Freigabebuff haben.",
I could not find the last two options in the Grid menu, are they already implemented?
Whoups. That comes from (yet) another patch for GridStatusAura, I'll remove them. The patch handles the different "abolish" buffs (abolish disease, abolish poison) and their effect on the corresponding status.
Modify the "By Group 10 w/ Pet" or whichever you want in GridLayoutLayouts.lua and change the class filter on the pet group to be just "HUNTER" instead of "HUNTER,WARLOCK". You'll probably want to feed your modified layout in through an external addon so it's not overwritten each time you update; take a look at the GridLayoutForHealers addon for an example of how to do this.
It seems like it can take a few seconds between a pet being summoned and the Grid background being resized.
Is that with the pet being near the player ? The only way I see where this kind of latency could occur is if RosterLib postpone to acknowledge the unit (because it has UnitName() == UNKNOWNBEING). Or maybe you're talking about solo with pet ? I'll have to check that.
Take a look at the following patch to RosterLib :
--- Roster-2.1/Roster-2.1.lua (revision 46504)
+++ Roster-2.1/Roster-2.1.lua (working copy)
@@ -256,9 +256,9 @@
if not owner then return end
-- get ID
- if owner:find("raid") then
+ if owner:find("raid", nil, true) then
return owner:gsub("raid", "raidpet")
- elseif owner:find("party") then
+ elseif owner:find("party", nil, true) then
return owner:gsub("party", "partypet")
elseif owner == "player" then
@@ -277,12 +277,7 @@
unknownUnits[unitid] = nil
- -- some pets never have a name. too bad for them, farewell!
- if not name and unitid:find("pet") then
- unknownUnits[unitid] = nil
- changed = changed or c
+ changed = changed or c
if changed then
@@ -292,9 +287,10 @@
- if next(unknownUnits, nil) then
- self:ScheduleEvent("ScanUnknownUnits", self.ScanUnknownUnits, 1, self)
+ if next(unknownUnits) then
+ if not self:IsEventScheduled("ScanUnknownUnits") then
+ self:ScheduleEvent("ScanUnknownUnits", self.ScanUnknownUnits, 0.5, self)
@@ -392,7 +388,13 @@
- unknownUnits[unitid] = true
+ local count = (unknownUnits[unitid] or 10) - 1
+ if count > 0 then
+ unknownUnits[unitid] = count
+ -- ChatFrame1:AddMessage("RosterLib: Unable to associate a name with "..unitid.." after 10 tries.")
+ unknownUnits[unitid] = nil
I think it might help.
I also committed a change to the branch that might help in the matter.
Just wondering how far off this branch is from going into the trunk?
It seems to be working beautiful
There is still an issue with some pets appearing as completly black frames. This is a bug in the Secure header code, that allows units even when UnitName(unit) == UNKNOWNOBJECT.
If someone with access to the official US UI Forum could ask that the following patch is applied to SecureTemplates.lua :
--- SecureTemplates.lua 2007-08-10 10:53:52.000000000 +0200
+++ SecureTemplates.lua.new 2007-09-03 10:06:33.000000000 +0200
@@ -1075,7 +1075,7 @@
if not ( useOwnerUnit ) then
unit = petUnit;
- if ( UnitExists(petUnit) ) then
+ if ( UnitExists(petUnit) and (filterOnPet and name or UnitName(petUnit)) ~= UNKNOWNOBJECT ) then
if ( name and
((not strictFiltering) and
(tokenTable[subgroup] or tokenTable[className] or (role and tokenTable[role])) -- non-strict filtering