Sometime the compare tips are blank... my theory is that it's only the first time you compare to the item, or maybe the first time you do a compare at all, after a full login (not reload). Like the client doesn't yet know what your items are, and has to query the server for a tooltip.
BUT it's not done that consistently to me. If this is the problem and it happens to me consistently enough that I could test, I have a few solutions cooked up (mainly requesting every slot's tooltip on login, so they're cached before the user requests one)... but... yea... I can't say I've seen the blankies lately.
Ahso, yea my only complaint about the compare API is it doesn't compare ammo, but that's a minor annoyance considering that there's so few ammo upgrades, and there's always a very clear path (you don't have to sit there weighing options, just grab the higher DPS).
I just took a quick look at Examiner... yikes. It looks like it's got an assload of features, and of course the addon is massive. If I were you, I'd ask myself what bits of that addon you find a vital need, and replace it with something much smaller. But then again, that's the whole reason I wrote tK, because I thought the same thing about EquipCompare and EQC.
For what it's worth, this is most likely the offending code:
-- Equip Compare Tip
if (not Examiner.statTooltip) then
if (IsShiftKeyDown()) and (not ShoppingTooltip1:IsVisible()) then
elseif (not IsShiftKeyDown()) and (ShoppingTooltip1:IsVisible()) then
It's completely overriding everything here... tK, the default UI, any other compare addon... it's FORCING the compare tooltips to hide if shift is not held down. Talk about being an imposing asshole.
Well found a workaround, leave appearance module turned on but select borders to "none", so welcome TK, only issue is the same as posted above, no compare from the inspect frame without clicking shift :(
And as I said above, the default inspect UI works, which means you have an addon breaking this, which is something tK can't (and shouldn't have to) fix.
The version of tK before they added the compare API was not much bigger. The main file was roughly twice the size it is now (was 102 lines, now 61)
The primary difference is, tK has no config options, because it doesn't need them. That cuts out the need for libs to hand DB, config, etc. I don't need OO or Hooks (hooking manually is much faster and in the end safer for me)... No locale needed (tho EQC's is rather small)... Also no support for all those addons that create their own tooltips needlessly... GameTooltip works just fine for GUIs people!
I get tK tips just fine in the default inspect window, which means that some other addon is making that go away, which is, again, something I'm not responsible for :P I will tweak the position a tad, it was something that never really bothered me enough to go find the value and fix it.
Oh and, if you'd like a comparison:
tK: 3.47 KiB, everything
EQC: 22.66 KiB core (with locales), 283 KiB libs
Sure it's not much difference if the libs are reused in another addon (*only* a 6.5x difference in size)... but mine is tiny even if it's the only addon loaded. Hell, I think tK is even smaller than the default UI's compare tip code.
tK is not abandoned, it has not need any updates. Border issues are caused by Cowtip, not exactly something I can fix. I don't do any fancy majicks, just set the compare tip and position it, same thing the default UI does.
Users of my mods know that, the smaller they are, the less often they need repairs. tK is roughly on screenful of code.
Fisheye is just indexing my gcode SVN. The gcode link you posted are download I've specifically released. You know, that thing people keep saying about how WAU should pull down tagged tested releases instead of trunk alpha/betas? Yea, gcode downloads (and WoWI) are my tested versions :)
tK had 4 self-made tooltips before, now it has two (so you can open the ItemRef tip and a normal tip at the same time and get compares for both)... so skinner should be updated to remove two of those old tooltips. The other two I use now are the default UI's.