Originally Posted by MunkDev
Why wouldn't you be able to? As long as the code that moves it is signed and untainted, there are no issues with protected frames anchoring to each other.
Setting a point for a frame out of combat doesn't spread taint.
To prove my point, I created a secure action button, anchored it to LootFrame, which is completely unprotected and moved around in combat to follow the mouse cursor.
The LootFrame code, however, is not tainted and is moved around by signed Blizzard code. Therefore, no problem.
Try it yourself:
Lua Code:
local f = CreateFrame('Button', 'JustASecureButton', LootFrame, 'SecureActionButtonTemplate, ActionButtonTemplate') f:SetPoint('TOPRIGHT', LootFrame, 'BOTTOMLEFT') f:SetAttribute('type', 'action') f:SetAttribute('action', 6) f.icon:SetTexture(GetActionTexture(6))
There seems to be a lot of misconceptions about taint floating around. |
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.
Here is the code where the Blizzard code could decide to move the MultiBars at any time:
https://github.com/Resike/BlizzardIn...ua#L2709-L2713
You pull a boss, combat locks down, boss frames show up (or not), MultiBarLeft and MultiBarRight gets pushed to the left on the x axis (or not) TargetFrame (protected) are anchored to the MultiBarRight, so basically you try to move a protected frame in combat. And bang you get blamed for the whole taint, even tho you set your initial position seucrely and did't tried to move anything in combat.