NotifyInspect, INSPECT_TALENT_READY, and targetting yourself

Sheltim · 07/16/08, 9:07 AM

I'm debugging a mod that inspects your target. It (roughly) uses the following:

self:RegisterEvent("INSPECT_TALENT_READY", "DoSomething");
NotifyInspect("target");

Now, normally this works fine. There's sometimes up to a few second delay from calling NotifyInspect and receiving the INSPECT_TALENT_READY event. As expected. However, when I have myself targeted, it takes an extraordinary amount of time. I've let it sit for a few minutes and gave up after that.

I've looked at WoWWiki, WoWDev, and WoWProgramming.com. None of them have a reference to this sort of problem.

Does anyone have any ideas of what might be going on, what I might be doing wrong, or how to further debug this? Has anyone encountered a similar situation? Is there something special that I have to do with NotifyInspect when using "target" with myself targeted?

funkydude · 07/16/08, 9:19 AM

Did you actually use "me"? It's "player" not "me".

Sheltim · 07/16/08, 9:28 AM

Originally Posted by funkydude

Did you actually use "me"? It's "player" not "me".

Sorry about that. I do realize it's "player" and not "me", but I was just trying to give context. The code actually uses "target" in all cases. The problem is when I have myself targeted. I'll edit my OP for clarity. Thanks

EDIT: I just got a response from Akryn:

if UnitIsUnit("target","player") then
    CheckWhateverYoureCheckingLocallyInsteadOfInspectingSinceYouCantDoThat()
    return
end

btw, it's also a good idea to hooksecurefunc on NotifyInspect, so that you can tell if some other addon called it after you did but before you get the info back, which means you'll need to discard that data unless it's on the same unit.

This implies that ITR simply won't fire when the "target" is "player". Is that true?

Vodrin · 07/16/08, 10:26 AM

try;

if UnitIsUnit('player','target') then NotifyInspect("player"); else NotifyInspect("target"); end

No idea if it will help or if its the correct syntax but might do the job. Otherwise it may just be that you can't inspect yourself.

Gearknight · 07/16/08, 11:15 AM

Trying to inspect yourself in-game certainly doesn't seem to do anything.

Sheltim · 07/16/08, 11:36 AM

Originally Posted by Vodrin

try;

if UnitIsUnit('player','target') then NotifyInspect("player"); else NotifyInspect("target"); end

No idea if it will help or if its the correct syntax but might do the job. Otherwise it may just be that you can't inspect yourself.

That's an interesting idea, I'll give it a try.

Originally Posted by Gearknight

Trying to inspect yourself in-game certainly doesn't seem to do anything.

Odd: inspecting yourself via right-click doesn't work, but something like "/script InspectUnit("player")" does work.

Shadowed · 07/17/08, 5:02 AM

If you try and inspect yourself INSPECT_TALENT_READY never fires, my guess is because the client already knows your talents/gear/ect so theres nothing to request, if you notice when you do InspectUnit("player") it shows gear fine but the talents don't actually show up.

What Vodrin gave was close, you want something like.

if( not UnitIsUnit("player", "target") ) then
     self:RegisterEvent("INSPECT_TALENT_READY, "DoSomething")
     NotifyInspect("target")
end

If you want to show the players talents when they target themselves then

local firstPoints = select(3, GetTalentTabInfo(1)) or 0
local secondPoints = select(3, GetTalentTabInfo(2)) or 0
local thirdPoints = select(3, GetTalentTabInfo(3)) or 0

local spec = string.format("%d/%d/%d", firstPoints, secondPoints, thirdPoints)