Page 1 of 1

Serious Inspection Error

Posted: Sun Nov 06, 2005 11:55 pm
by SoulDrake
Hi there. I've run into a bug that occurs consistantly whenever I go to inspect somebody. How the bug happens is when I first inspect them initially, and then go look at their Honor stats. When I switch back to looking at their equipment, this is where the errors come in. Every time I try to look at an item in a given slot, I get no tooltip showing up at all, and get an error instead. Some of the errors read as follows:

Error: [string "InspectShoulderSlot:OnEnter"]:3: Usage: SetInventoryItem(unit, slot [, nameOnly])

Error: [string "InspectNeckSlot:OnEnter"]:3: Usage: SetInventoryItem(unit, slot [, nameOnly])

Error: [string "InspectTabardSlot:OnEnter"]:3: Usage: SetInventoryItem(unit, slot [, nameOnly])

Error: [string "InspectShirtSlot:OnEnter"]:3: Usage: SetInventoryItem(unit, slot [, nameOnly])

Error: [string "InspectHeadSlot:OnEnter"]:3: Usage: SetInventoryItem(unit, slot [, nameOnly])

And finally, this is the initial error that I get upon looking back at the equipment:
Error: ...\AddOns\Blizzard_InspectUI\InspectPaperDollFrame.lua:58: Usage: SetUnit("unit")

This goes on for every other slot that can be inspected. I can only temporarily fix this problem by reinspecting them. But, the problem will always show up again if I inspect somebody, look at their honor, and then look back at their equipment. It is also unavoidable because if I go to inspect somebody else after looking at another person's honor, it starts by looking at their honor, and so when i go to look at the new person's equipment, the toon of the last person I inspected shows up instead and the same errors occur.

I don't know what to do about this. I have the latest version of Census+, and I have even tried disabling all other UI mods to see if they may be partly responsible, but the errors still occur as I have described with only Census+ mod running alone. Thanks for taking a look at this issue.

Posted: Mon Nov 07, 2005 5:25 am
by SciTzo
I have the same problem, but i didnt know it was Census+ that was the course. I use the GoodInspect mod too, and so figured that mod was the reason for the errors.

But i can confirm the the error occurse when switching back to characterview after looking at the honor tab. And that the errors are gone if you reinspect the person.

Posted: Mon Nov 07, 2005 9:28 am
by Rollie
Thank you for this information. THis is the first I have seen/heard about it and I will get to work on fixing this tonight.

Posted: Mon Nov 07, 2005 9:49 am
by Hybuir
I got this too, but since the error didn't say CensusPlus anywhere I just disregarded it as a C+ error :|

Posted: Mon Nov 07, 2005 10:49 pm
by Skyfire
I also receive this, but I attribute it to the shift that Blizzard made (moving some of their systems to Mods).

Note it says Blizzard_InspectUI =)

Posted: Tue Nov 08, 2005 2:25 am
by SciTzo
Skyfire:
I think you're partly right. From what i can see the shift Blizzard made caused the errors in Census+.

And its easy to test, just disable Census+ and the errors are gone. (tested it last night)

Posted: Tue Nov 08, 2005 4:21 pm
by Gast
I have the same errors. I also thought GoodInspect was to blame and never tried to just disable CensusPlus.

Posted: Tue Nov 08, 2005 8:27 pm
by Rollie
I'm working on getting this all working smoothly. In the meantime, if it bothers you too much, at the top of CensusPlusProfiler.lua in the /World of Warcraft/Interface/Addons/CensusPlus directory, you can simply change

Code: Select all

 myCPProfile_ENABLED 				= 	1;	-- Enable the profiler?
to

Code: Select all

 myCPProfile_ENABLED 				= 	0;	-- Enable the profiler?
on line 10 to disable the profiler section.

Posted: Sat Nov 12, 2005 5:00 am
by Gast
Shouldn't it be set to "nil" instead of "0"? I have set this variable to nil for quite some time now and still get the error. Well, I will try to set it to 0. Maybe that helps.

Posted: Sat Nov 12, 2005 12:09 pm
by Rollie
Actually I looked into this the other day and what I posted above will not fix it.

I will be releasing a new version very soon that will address this. I will try to add a post later that will detail how to fix this if you want to just fix it for now.