Most of the afore mentioned problems with SecureButtons and blocked addons have been resolved with the new testrealm patch (a wronng variable name in SecureStateDriver.lua was the cause). But when using SecureStateDrivers the UI is still blocked.
Therefore I made a small sample code that creates an empty button which maps to action 1 normally and to action 2 when stealthed. This works fine on live-servers but gives the UI-blocked error on test-servers. Does anyone see any problems with this code that would make it disfunctional with 2.1? If not, would someone with an US account be so kind and post this problem on the WoW US UI&Macros forum?
Code:
local header = CreateFrame("Frame", "TestHeader", UIParent, "SecureStateDriverTemplate");
header:SetAttribute("statemap-stealth-1", "2");
header:SetAttribute("statemap-stealth-0", "1");
local button = CreateFrame("CheckButton", "TestButton", UIParent, "SecureActionButtonTemplate, ActionButtonTemplate");
button:SetAttribute("type", "action");
button:SetAttribute("showstates","*");
button:SetAttribute("statebutton","1:state1;2:state2");
button:SetAttribute("*action-state1", 1);
button:SetAttribute("*action-state2", 2);
header:SetAttribute("addChild", button );
header:SetAttribute("state","1");
button:ClearAllPoints();
button:SetPoint("CENTER",0,-50);
button:Show();
header:ClearAllPoints();
header:SetPoint("CENTER",0,-50);
header:Show();