Originally Posted by Resike
First the two things are completely different. The guy here SetPoints a protected frame to another protected frame, which gets moved in combat by Blizzard, without restrictions, and without any secure code, just because Blizzard can do that. And when that happens that code will get blamed whoever called the initial SetPoint, it does not matter if that SetPoint was called securely or not.
|
They are not different; Blizzard code does not adhere to combat lockdown, regardless if it's moving protected or unprotected frames, which is why I posted that video as proof. Creating a secure child frame will also make the parent inherently secure, so if what you're saying is true, LootFrame would go bonkers with the code I posted, but it doesn't. Using SetPoint out of combat does not spread taint and your addon will not get blamed for anything if you do.
Please, Nimhfree, post your
entire code for the whole addon if you haven't already. I'm 99% sure your problems come from somewhere else.