Comment #3

no-reply@curseforge.com (ithilyn) — Mon, 25 May 2009 04:08:32 +0000

Hi ckknight, looks like there was a change when dual specs rolled out that's affecting the TalentSpec tag. I finally tracked it down after wondering why so many people were coming up 0/0/0 in my cowtip. GetTalentTabInfo() now has a 4th arg to specify which talent group you want to read from, and you can determine which is active by calling GetActiveTalentGroup(). Take a look at the updated blizzard frame code:

http://wowcompares.com/3129901/AddOns/Blizzard_InspectUI/InspectTalentFrame.lua

Please take a look at the following patch and see if you can roll it into LibDogTag-Unit-3.0/Categories/Talent.lua. It seems to be working for me, people that used to come up with 0/0/0 now come up with their correct talents, and I verified them with the blizzard inspect frame (right click -> Inspect). Thanks so much!

I can't seem to post a code fragment here, here's an offsite link:

http://ithilyn.com/WoW/Talent.lua.diff

Real simple. Hope there are no concurrency issues.

I noticed someone had filed a feature request under cowtip maybe to expire talent entries after a while. With easy respecing now this would be nice to expire them after a few minutes or something.

Comment #1

no-reply@curseforge.com (Failwarrior) — Mon, 13 Oct 2008 08:08:15 +0000

Stop breaking my pitbull!

Comments about LibDogTag-Unit-3.0

Comment #3

Comment #1