Applyed workaround for the Action Blocked message when using /click macros

Apparently the cache for the click-frames taints its first element after frame creation, so a one-time call of GetClickFrame() after frame-creation removes that tainted element from the cache, and all future calls return the proper secure frame. [1]

[1]: http://forums.worldofwarcraft.com/thread.html?topicId=3773503744&sid=1&pageNo=4#60
This commit is contained in:
Hendrik Leppkes
2008-09-16 15:42:39 +02:00
parent af35db6328
commit c8e4068fa6
+3
View File
@@ -24,6 +24,9 @@ function Bartender4.Button:Create(id, parent)
local absid = (parent.id - 1) * 12 + id
local name = ("BT4Button%d"):format(absid)
local button = setmetatable(CreateFrame("CheckButton", name.."Secure", parent, "SecureActionButtonTemplate"), Button_MT)
-- work around for "blocked" message when using /click macros
GetClickFrame(name .. "Secure")
button.rid = id
button.id = absid
button.parent = parent