"This should actually be avoided in TipTop as I do not check for talents if the default Inspect window is open."I did this on purpose in TipTop to avoid the error in the default client. It *is* an error in the default client. My addons do "play nice with WoW". This is a documented error. And the addon I recommended to fix it (if for some strange reason you're still seeing the error with only TipTop enabled, which I haven't seen that error in a long time myself) really does exist. Perhaps the author of TipTac just incorporated InspectFix into TipTac itself.And, of course the game causes no errors without addons. The error is caused by the Blizz code not checking the GUID of the unit returned by an inspect query of an addon. This GUID arg was added for a reason by Blizz so that addons would not step on eachother's toes when inspecting, but the Blizz UI forgot to account for it in the InspectFrame code.I gave you a solution. /shrug I know fully well what that error is and what causes it. I've seen it plenty of times by users of plenty of addons. I have no idea why your TipTop would be asking the server for inspect information when the default InspectFrame is open. I specifically have it set not to in the code.(Interface: TipTop | Bug: Lua Error on Inspect)
↧