Closed mixxorz closed 4 years ago
I literally have no idea why it does what it does.. or why this does anything to resolve it.. but figured I should share it at least.
By simply adding return self.db.profile to the end of the Core:OnInitialize() in init.lua I no longer have any issue with spy on Classic. It doesn't even have to be return self.db.profile.. at first I had DevTools_Dump(self.db.profile) and it seemed to work. As long as you're some how calling the array specifically.
What I do know is, that minor change allows this db table to contain the missing variables.
Thanks for helping with debugging!
I've made a recent change with db, do you mind trying version 1.4.1 and see if that works?
From what I can tell, it works so far on Classic.
Sorry just to confirm, is it working now with Spy on Classic?
Yes. SpyClassic1.1.1-release is currently working along side Glass-1.4.1-classic.
That's awesome!
Basically I was doing something weird with the AceDB saved variables and I think that was having unintended consequences with Spy (but curiously, no other addon). Release 1.4.1 fixes the AceDB issue, which seems to have fixed Spy compatibility as well. Awesome!
I'll close this now. Thanks for debugging!!
Describe the bug Spy does not work with Glass.
https://www.curseforge.com/wow/addons/spy
Possibly because Glass modifies the Combat Log.