incorrect Talent on tooltip and HUD
 

I don't know if anyone else is having this problem... but i've recently noticed that the HUD and tooltip shows the incorrect talent that the person clicked on or hovering over has..... for example... sometimes when i click on a sum1 that i know is Balance Spec druid (because i inspected him).. the HUD and tooltip shows him as Resto spec druid...

this happens for all classes not just druids... so i'm wondering if this is a fixable problem.... i've tried reinstalling and turning nUI on just by itself with no other addons... that didnt work..

This is a known problem when dealing with more than one addon handling inspect queries. In my case altoholic does inspect queries on my alts which are correct but the nUI screen info is wrong. But I am guessing that if I only had nUI installed it will work fine. I will check and confirm that after Ive had some sleep.

Recently I was running without nUI (too much lag for a healer in 25 man which may have been from some of the other addons I was running, so I went almost default UI) and I had the same problem as this, so it is not nUI specific.

Saying that, I have no idea how to fix it, sorry ;)

There is also the issue of characters that are dual-spec. I'm not sure if nUI was updated to take this into consideration. If a druid showed a warrior spec, for example, then what Xrystal suggested may be the problem. But if all incorrect readings seem to be for the same class, then that character is using their secondary spec, but nUI is just checking for their primary.

If this is the case, scott, and you're not sure how to update it, just shoot me a PM or look at my tooltip mod.

Yes, it is as you suspected.

We could hover over a druid and it would show a paladin spec. Even on inspect it would show up the wrong tree and usually throw up a hunter tree as if it was the default tree if none was selected.

Fortunately our guild run with a few selected pugs so we have gotten to the point where at least I know what spec everyone is and don't need to worry about it.

If that's the case then nUI isn't watching for other addons that call NotifyInspect. Unfortunately, the inspect system assumes that only one addon or the Bliz UI will use it at a time, so if one addon requests talent data, and then another addon requests talent data before the first request comes back, the only answer that comes back will be the second one. There is no indication other than the talents themselves which class or player the response is for; so really the only good solution is to secure hook NotifyInspect, and if you weren't the one that called it, ignore the next result and try again (possibly after a backoff delay).

Yeah -- that's been a struggle from the get-go since I added talent inspections to nUI. I hadn't tought of hooking NotifyInspect though... thanks for that tip... I should be able to avoid much of the conflict that way.

I had tried implementing LibTalentQuery into my tooltip addon and could not get it to work at all... Some day I'll try to work inspects better. PITA. :)

Thread derail landing in 5...4...3...2...1

Thread derail now landing on runway 19.

MMMM.... I LOVE PITA!

Thread derail? What thread derail? Did anyone see a thread derail around here? Nope! Not me! Never seen one of those before!

I have had a conversation with Bliz on the subject and they've indicated fix is in the offing, but I don't know what or when... just that they see the problem and it's on the to-do list. What I've been asking for is some information in the TALENT_INSPECT_READY event such as the GUID as an argument to the event which at least would allow the client to conclusively know if the inspection that was triggered was the one that was asked for or expected.

What about PETA?

Yeah.... Not so much...

Thanks for that. :) Would be very nice.