Blizzard_InspectUI\InspectGuildFrame.lua Error

[Mabrah]

Originally Posted by Miabella I've been getting that error repeatedly this week. The only addons I have that you have are Omen and Titan.

I've disabled both Omen and Titan while leaving nUI enabled and the error still occurs. The only time I don't get the error is when I disable either nUI or TipTop, or both.

I'm baffled. lol

[spiel2001]

I'm curious -- if you try nUI6 instead of nUI5 and run that with TipTac, do you still get the error?

[Mabrah]

Originally Posted by spiel2001 I'm curious -- if you try nUI6 instead of nUI5 and run that with TipTac, do you still get the error?

Just installed nUI6, the error does not occur with it.

[spiel2001]

Well, that's good news. But I'm still baffled.

*scratches head*

[todd0168]

I am using nUI6 and I do get this error constantly. I will have to go through my addons and see if I can't figure out which one is causing the grief.

[Belechannas]

I am getting the same error (I wouldn't say "all the time" but once every hour or two) with nUI5.

Just speculating, but it may have nothing at all to do with any specific addon. The recent pattern seems to be that some valid calls to Blizzard addons just fail for no apparent reason. It could simply depend on where various addons are loaded in memory, and have nothing to do with their actual code. In other programs I've debugged, this type of behavior can result from data or pointers getting corrupted or improperly initialized (in this case, probably inside the client rather than Lua code).

Since nUI has a relatively large memory footprint compared to most other addons, it would probably be more likely to be "in the wrong place at the wrong time" in memory.

[nilla151]

is anyone else getting this error on only one character. for example. my paladin does not get this error, however my warrior(my main) gets it every few seconds or so. from picking stuff up opening my map ect. evebn just walking i get it. but on my paladin this error is completely nonexistant

[spiel2001]

Do you have any addons enabled for your warrior that are not enabled on your Pally? That would be the first place I would look.

[nilla151]

no everything is exactly the same. i did think of that initially and checked. but it's exactly the same. the only thing different is location of my grid and tauntmaster. but i highly doubt the location could cause it. it wasnt doing t before but no i logged back in it's still doing it.

[spiel2001]

Just for giggles... try exiting WoW and renaming your [ World of Warcraft > WTF ] to [ World of Warcraft > WTF.saved ] and lets see if there's some saved variable data causing the headache. You can exit WoW again and rename it back after you do the test.

[Longstreet]

omg. i am getting this error all the time ever since i started playing wow again. im pulling my hair out.

i only run with deadly boss mods, quartz and recount.

[tinyu]

yeah this error is annoying but it wont be getting fixed as scott is working on nUI6

theres also problems with the buff display and pet happiness and pet bar and worgen unitframes not displaying properly.

[SDPhantom]

I've had this error pop up through my own addon code for a while and it's completely in Blizzard's UI. If Blizzard_InspectUI loads for any reason, even manually inspecting a player through Blizzard's own menus, the Inspection UI registers for the INSPECT_READY event. If this event were to fire at all while the inspection window is closed, it runs into an error with the stored UnitID being nil.

The following is a modified version of patch code I wrote a long time ago to fix this problem.

local function patch()
    local oldfunc1=InspectPaperDollFrame_SetLevel;
    InspectPaperDollFrame_SetLevel=function(...)
        if InspectFrame.unit and UnitExists(InspectFrame.unit) then
            return oldfunc1(...);
        end
    end;
 
    local oldfunc2=InspectGuildFrame_Update;
    InspectGuildFrame_Update=function(...)
        if InspectFrame.unit and UnitExists(InspectFrame.unit) then
            return oldfunc2(...);
        end
    end;
end
 
if IsAddOnLoaded("Blizzard_InspectUI") then
    patch();
else
    local eframe=CreateFrame("Frame");
    eframe:RegisterEvent("ADDON_LOADED");
    eframe:SetScript("OnEvent",function(self,event,arg)
        if event=="ADDON_LOADED" and arg=="Blizzard_InspectUI" then
            self:UnregisterEvent(event);
            patch();
        end
    end);
end

[tinyu]

Originally Posted by SDPhantom I've had this error pop up through my own addon code for a while and it's completely in Blizzard's UI. If Blizzard_InspectUI loads for any reason, even manually inspecting a player through Blizzard's own menus, the Inspection UI registers for the INSPECT_READY event. If this event were to fire at all while the inspection window is closed, it runs into an error with the stored UnitID being nil. The following is a modified version of patch code I wrote a long time ago to fix this problem. local function patch()     local oldfunc1=InspectPaperDollFrame_SetLevel;     InspectPaperDollFrame_SetLevel=function(...)         if InspectFrame.unit and UnitExists(InspectFrame.unit) then             return oldfunc1(...);         end     end;       local oldfunc2=InspectGuildFrame_Update;     InspectGuildFrame_Update=function(...)         if InspectFrame.unit and UnitExists(InspectFrame.unit) then             return oldfunc2(...);         end     end; end   if IsAddOnLoaded("Blizzard_InspectUI") then     patch(); else     local eframe=CreateFrame("Frame");     eframe:RegisterEvent("ADDON_LOADED");     eframe:SetScript("OnEvent",function(self,event,arg)         if event=="ADDON_LOADED" and arg=="Blizzard_InspectUI" then             self:UnregisterEvent(event);             patch();         end     end); end

and where would i paste this?

[SDPhantom]

It's completely self-sufficient Lua code, you can make an entire addon out of it or just paste it at the base of any other addon.

The original version of that code was in the sandbox file of my personal dev addon that used an addon load hook API I wrote in the core of the dev addon.

[oscarucb]

The latest version of InspectFix on curse solves all the problems mentioned in this thread:

http://wow.curse.com/downloads/wow-a...nspectfix.aspx