WowAce

Blizzard uses GetAverageItemLevel() to get the average ilvl of the player. I don't think there is an API to get the average ilvl of other players. However, they use all items including those in your bags/bank to calculate the max possible ilvl. I think that's the reason why their number is different. InspectEquip calculates the average ilvl of the currently equipped items (except shirt/tabard, but I guess Blizzard excludes those too).

Yeah, I know :( That will be changed in the next update, too.

Where can you see the official item level of another player?
If you're talking about the value in the character panel (for your own character), that's the average item level of your highest ilvl items and not necessarily the item level of your currently equipped items. E.g. during leveling you receive lots of green items, which have higher ilvl than lvl 80 epics (AFAIK Blizzard doesn't distinguish between green/blue/epic in the ilvl calculation, so a 278 green > 277 epic). Could be because of that... But I'll check if they maybe use different weights for different slots in their calculation or something.

@yoshimo: It currently only checks if the item is enchanted, not if it is gemmed - because gem information was sometimes not immediately available pre 4.0 and I didn't want to incorrectly mark all items as ungemmed. I'm not sure if this works reliably now (well, inspect doesn't really work reliably at all in 4.0.1), but a gem check is on my todo list. I just don't have much time for WoW and addons right now, and the #1 priority is getting InspectEquip ready for cataclysm (mostly adding the new items, currencies etc.).

Thats a good suggestion, thanks. I'll probably do that once I find time for it.

Yeah, inspecting is currently *very* buggy in 4.0.1. It's a known issue (http://forums.worldofwarcraft.com/thread.html?sid=1&topicId=27188060299) and hopefully Blizzard will fix it soon (4.0.1a probably).
I've tested this quite a bit, and the same problems occur with no addons loaded, so I'm quite sure this is not an addon problem. Inspect just sometimes (e.g. once you enter an instance, it doesn't work anymore) breaks and doesn't work until WoW is restarted.

Thanks for the info! Looks like Jncl updated the Skinner skin for InspectEquip, so hopefully it works now :)

@Althena: Concerning the T10.25, the T7/T8 sets are labelled T7.0/T7.5 etc. in InspectEquip. I didn't use that naming system for T9 and T10 because there are now 3 sets (emblems only, 25 man, 25 man heroic) and there are quite a few different naming schemes (T10.0/T10.5/T10.75, T10.251/T10.264/T10.277 etc...), so I decided it would be better to just use the same set name for all. They differ in source however. The ilvl 251 items have source "Emblem of Frost", ilvl 264 comes from "Icecrown Citadel-25" and ilvl 277 from "Icecrown Citadel-25 (heroic)". I think that's the best solution. (Thankfully we won't have that problem in Cataclysm :))

Concerning the "-Shadow", I assume that means it's the shadow priest T10 set? That's actually a nice idea. I didn't add the class because it's kinda obvious (you can't wear other classes set items), but for hybrid classes it is indeed interesting to see if they're using the shadow or healing set for example. Maybe I'll add that in a future version, but unfortunately probably not before Cataclysm. (I'm going to change the database and right now it's not so easy to modify it to include information like that. Also, it would need to be translated to all languages, which is not the case with the simple "T10". That's not possible with the current format.)

Well, I've tried everything you said - replacing tabars while the InspectEquip panel is open, looting reward bags, moving items in my bag... - but unfortunately I can't reproduce it. No matter what I try, the window does not even move a pixel. I'd say this must be a problem with another addon interfering (like I said, there is absolutey no code in my addon that tells it to move the window anywhere). Unfortunately there is no way I can fix it, when I can't even reproduce it, sorry :(
Maybe you can try (temporarily, of course) disabling some other addons to see if the problem still occurs. That way you should be able to find out which other addon needs to be enabled so that the bug occurs. Maybe we can find a solution then... :\