Get an Epic Experience with Premium

WhoHas

Bags & Inventory Login to Add Favorites
  • 1 Like
  • World of Warcraft
  • 58 Monthly Downloads
  • Supports: 5.0.5
  • 22,440 Total Downloads
  • Updated 09/23/2012
  • Created 08/19/2007
  • 347 Favorites
  • Project Site
  • Comments
  • Release Type: Release
  • License: BSD License
  • Newest File: 5.2.0
or

About WhoHas

WhoHas modifies every tooltip in the game to show which of your characters have the item in the tooltip, and where. This works in your inventory, at the auction house, on chat links, and even in trade skill windows. The tooltip will show how many of the item each of your characters have, and where - in their inventory, in the bank, equipped, or even in their inbox. This can be useful for managing your overall inventory, or for finding out who has the items you need for crafting.

WhoHas requires a separate addon to track all of your personal items. WhoHas currently supports:

WhoHas will auto-select the best backend to use based on the inventory addons you have enabled. It will search for addons in the order shown above. I may be able to add support for other inventory addons on request.

WhoHas supports English and is partially translated into German and French, thanks to the efforts of Pelion, and more recently, TorenAltair. If you would like to help finish the German and French translations, please let me know.

To prevent WhoHas from showing tooltips for specific items, enter "/whohas ignore ITEM NAME" in chat, where ITEM NAME is the item you don't want WhoHas tooltips for. You can also type "/whohas ignore " (make sure to include the space at the end) and then shift-click on the item you want to ignore to fill in its name.

Code hosted by GitHub

The source code for WhoHas is hosted on GitHub at https://github.com/rvaughn/wow-whohas.

  • Completely rewrote the Armory scanner. WhoHas should now support future versions of Armory better.

Comments

First Previous Page 3 of 17 Next Last
  • #211
    Forgot to mention I am also using the Anywhere Bags plug in. I'm not certain if that makes a difference.
  • #216
    Well, actually it's not that something changed in Baggins.... it's that WhoHas doesn't support Baggins... yet. I will see if I can get that in place this week.
  • #214
    Hi - sorry about the delay, Curse failed to notify me about your comment, or my spam filter ate it.

    Very likely something has changed in Baggins that breaks WhoHas now. If you can paste an error message that will help, but I'll look into it in the meantime. I haven't tried it with Baggins in a long time.
  • #205
    Gruma, using the most recent version and switching back to link armory versus possessions, I am getting a new thing in the mix.... seems whohas based on armory 411 are unmixy with TipTac, a tooltip handler. However, I get no errors when WH is tied to possessions.
  • #206
    Well, shoot. That doesn't make a whole lot of sense. I haven't changed anything that deals with tooltips. The latest change only affects how I interpret the Armory data in two little places. It's possible that it was previously erroring before it got to TipTac conflict.

    Anyway, I haven't used TipTac befotr, so I'll download it and check out the conflict.
  • #207
    Marblex, I have to ask you to post one of the errors again. I added in TipTac, and I'm not seeing any errors. I tried Armory r376 earlier and just updated to v9.2.6. I never saw an r411 "release".
  • #208
    Will do when I logon today :)
  • #209
    Can I assume you resolved your TipTac conflict since I haven't heard anything else lately? :)
  • #198
    Gruma thank you so much for working on this. Below are a list (just a sample) of errors caught by Bugsack. I can't make heads or tails, and this is not a complete list...but it appears to be all similar or the same...

    1x WhoHas-4.0.0b2\WhoHas.lua:235: bad argument #1 to 'match' (string expected, got table)
    WhoHas-4.0.0b2\WhoHas.lua:235: in function `NameFromLink'
    WhoHas-4.0.0b2\WhoHas_Armory_new.lua:47: in function `ScanChar'
    WhoHas-4.0.0b2\WhoHas_Armory_new.lua:32: in function `ScanAlts'
    WhoHas-4.0.0b2\WhoHas.lua:527: in function `UpdateCaches'
    WhoHas-4.0.0b2\WhoHas.lua:512: in function `ShowTooltip'
    WhoHas-4.0.0b2\WhoHas.lua:305: in function `OnShow'

    : ?
    TipTac-10.10.27\core.lua:806: in function `Show'
    MinimapButtonFrame-3.1.4\MinimapButtonFrame.lua:2133: in function `RollUp_OnEnter'


    Locals:
    link = {
    1 = "|Hitem:32494:0:3632:3507:0:0:0:2294529:71:0[Destruction Holo-gogs]"
    count = 4


    1x WhoHas-4.0.0b2\WhoHas.lua:235: bad argument #1 to 'match' (string expected, got table)
    WhoHas-4.0.0b2\WhoHas.lua:235: in function `NameFromLink'
    WhoHas-4.0.0b2\WhoHas_Armory_new.lua:47: in function `ScanChar'
    WhoHas-4.0.0b2\WhoHas_Armory_new.lua:32: in function `ScanAlts'
    WhoHas-4.0.0b2\WhoHas.lua:527: in function `UpdateCaches'
    WhoHas-4.0.0b2\WhoHas.lua:512: in function `ShowTooltip'
    WhoHas-4.0.0b2\WhoHas.lua:305: in function `OnShow'

    : in function `SetShapeshift'
    :"*:OnEnter":6: in function `OnEnter'
    Bartender4-3\StanceBar.lua:181: in function

    Locals:
    link = {
    1 = "|Hitem:32494:0:3632:3507:0:0:0:2294529:71:0[Destruction Holo-gogs]"
    count = 4
    }

    WhoHas-4.0.0b2\WhoHas.lua:235: bad argument #1 to 'match' (string expected, got table)
    WhoHas-4.0.0b2\WhoHas.lua:235: in function `NameFromLink'
    WhoHas-4.0.0b2\WhoHas_Armory_new.lua:47: in function `ScanChar'
    WhoHas-4.0.0b2\WhoHas_Armory_new.lua:32: in function `ScanAlts'
    WhoHas-4.0.0b2\WhoHas.lua:527: in function `UpdateCaches'
    WhoHas-4.0.0b2\WhoHas.lua:512: in function `ShowTooltip'
    WhoHas-4.0.0b2\WhoHas.lua:305: in function `OnShow'

    : ?
    QuestHelper-4.0.1.31b\collect.lua:26: in function `SetText'
    Interface\FrameXML\GameTooltip.lua:212: in function `GameTooltip_AddNewbieTip':


    Locals:
    link = {
    1 = "|Hitem:32494:0:3632:3507:0:0:0:2294529:71:0[Destruction Holo-gogs]"
    count = 4
    }
  • #199
    OK, excellent, that's something I can use. This is a conflict between changes in Armory and what WhoHas expects to see in its data. What version of Armory do you have?

    This is the reason I'm starting to convert WhoHas to use Armory's API like Warmexx suggested so long ago.
  • #200
    am using r75 just released aka 9.1.19. You and Warmexx rock and I'm glad to see these two great addons integrated :)

    Gruma, did you also write the now defunct WhoDrop? If so boy that could use a face lift for Cata :)

    Thanks again
  • #202
    Don't downgrade your Armory! Install the patched WhoHas I just uploaded instead.
  • #201
    Well... perhaps. If so, I just rock very slowly. :)

    No, I didn't write WhoDrop, it's just one of those coincidences of naming. WhoHas was basically the condensed form of what I was asking when I wrote it - "Who Has goldthorn?" for example. It's really a shining example of naming creativity. ;)

    OK, I finally reproduced your errors. I didn't get it at first with Armory v9.1.19, but I did after I updated to r376. I suspect v9.1.19 *is* a problem, I just didn't see it because I had to logout to save character data first.

    If you're able to, I would recommend downgrading to Armory v9.0.7 temporarily, and delete your Armory saved variables at the same time. That unfortunately means rescanning all of your characters too. If that's too much trouble, or if you really need the latest Armory, then don't bother. I didn't have any errors with this version though.

    I will try to come up with some sort of quick-fix workaround for this to get you going quickly. The real fix is for me to rewrite my Armory support, and that's going to take a little longer.

    BTW, BugSack is awesome, thanks for incidentally pointing that out! It's much, much nicer than Swatter.
  • #203
    Yeah I finally got on to BugSack when Improved Error Frame finally gave up the ghost and died in 4.01. I have tied WhoHas to possessions instead of armory for now (I use both) so it's not throwing errors. I will just wait till you and Warmexx synch up and I will switch the tagging back to armory then. For now WhoHas is working great :) And so is Armory :)

    ty again for all your work!
  • #204
    Just use b3 for now... it works correctly with the latest Armory versions, even if it doesn't do it the ideal way. Essentially it works the same way it always has, which means it isn't very future-proof.
  • To post a comment, please login or register a new account.
Login to Curse

Don't have an account? Create One.

Get an epic experience with Curse Premium
  • Faster addon downloads
  • Premium-Only Beta Giveaways
  • Ad-Free Curse experience
  • Premium Curse Client
  • and many More Features
  • Learn More »

Maingear

ENTER NOW