Originally Posted by LanceDH
Won't argue with that. Forgot something in your XML? Well I'm just going to tell you something went wrong in your LUA instead.
Edit:
As for everything LUA, this is unfinished and uncleaned code but I think we can all agree it burns people's eyes out.
|
Not exactly practicing what I preach, but you could just localize the widget to reduce bloat:
Lua Code:
local Left = PlayFrame:CreateTexture("$parent_L", "ARTWORK", 0)
Left:SetTexture("Interface\\AchievementFrame\\UI-Achievement-MetalBorder-Left")
Left:SetTexCoord(0, 1, 0, .87)
Left:SetWidth(16)
Left:SetVertexColor(bSat, bSat, bSat)
Left:SetPoint("topleft", PlayFrame, 15, -25)
Left:SetPoint("bottomleft", PlayFrame, 15, 25)
PlayFrame.left = Left
local Right = PlayFrame:CreateTexture("$parent_R", "ARTWORK", 0)
Right:SetTexture("Interface\\AchievementFrame\\UI-Achievement-MetalBorder-Left")
Right:SetTexCoord(1, 0, 0, .87)
Right:SetWidth(16)
Right:SetVertexColor(bSat, bSat, bSat)
Right:SetPoint("topright", PlayFrame, -15, -25)
Right:SetPoint("bottomright", PlayFrame, -15, 25)
PlayFrame.right = Right
On-topic:
I spent a lot of time trying to get this stuff sorted, because I use a fake cursor in ConsolePort that clicks on buttons and stuff in the interface. Since it had to be robust and refrain from tainting every single thing it touches, it uses the secure action button system along with a clickbutton attribute. The attribute is changed every time the user moves the cursor to another button, thus never calling any specific click scripts and never tainting the buttons it clicks.
The problem you're facing here is whether you can scan the spell book in a secure environment, which can only be done with secure handlers - and they offer a very limited part of the API. Also note that you can't reference non-secure frames in combat in a secure environment, meaning the paging buttons can't be clicked programmatically in combat using that approach. Personally, I think you should think of a different design to solve your problem.