Making Blizzard UI frame "transparent" to the mouse?

[acapela]

how would one go about hijacking an existing Blizzard UI frame (or any other frame, really) and rendering it completely transparent to the mouse?

the old Eclipse library (mentioned here) apparently did this (and i am happy to reverse-engineer stuff), but i cannot find any record of this library on Google or any of the main addon sites.

looking at other addons, it appears Frame:EnableMouse() and various "OnClick"/etc hooks might be relevant (and Button:RegisterForClicks() maybe not so relevant, not generally for frames), but i was hoping someone could point me directly to some documentation and/or an example (so i don't have to do a ton of trial/error).

thanks.

[Bitwise]

Drop this in a .LUA to have a frame in the center of the screen that you can click through. The final two functions called are what makes it work, theoretically they should work on any frame Blizzard or not.

local exampleFrame = CreateFrame("FRAME", nil, UIParent)
exampleFrame:SetWidth(100)
exampleFrame:SetHeight(100)
exampleFrame:SetPoint("CENTER", UIParent, "CENTER")
exampleFrame:SetBackdrop({bgFile = "Interface/Tooltips/UI-Tooltip-Background", edgeFile = "Interface/Tooltips/UI-Tooltip-Border", tile = true, tileSize = 16, edgeSize = 16, insets = { left = 4, right = 4, top = 4, bottom = 4 }});
exampleFrame:SetBackdropColor(0,0,0,1);

exampleFrame:SetFrameStrata(BACKGROUND)
exampleFrame:SetFrameLevel(0)

[Seerah]

Those two lines do not set whether a frame is click through or not, they merely set the frames draw level. (Think z-axis for your UI.) frame:EnableMouse(true or false) is what makes a frame click-through or not. (Your frame above is click-through by default)

[Bitwise]

Originally Posted by Seerah Those two lines do not set whether a frame is click through or not, they merely set the frames draw level. (Think z-axis for your UI.) frame:EnableMouse(true or false) is what makes a frame click-through or not. (Your frame above is click-through by default)

Yes, I suppose I should have mentioned that. I assumed he would already use EnableMouse(false) on his frame since he mentioned it in the first post. I'm not entirely sure which of those two lines sets it to be click-through, but i've seen EnableMouse(false) prevent you from clicking through but nothing happens if you click it. To test that, call Minimap:EnableMouse(false) and try to ping the minimap.

[Seerah]

That's because the MinimapCluster frame *behind* the minimap still has mouse enabled.

[acapela]

in my case, i am calling EnableMouse() on the ultimate "parent" frame of a group of frames, to disable the mouse, and never calling it in any form on any of the dependent/children frames.

the result of this is that the frame hierarchy rooted at the "parent" frame is not responsive to the mouse, but neither is anything else that happens to be underneath the "parent" frame.

so, i am guessing there is something else required. i have not been able to figure out what it is. Seerah's post implies that these child frames are not defaulting to something i don't want (and therefore should not be "blocking" the mouse even though the parent frame is disabled).

[Seerah]

I'm not sure if a frame's being mouse enabled is inheritable...

[acapela]

Originally Posted by Seerah I'm not sure if a frame's being mouse enabled is inheritable...

i was assuming that these children/dependent elements would default to "mouse disabled". but i can try experimenting with explicitly disabling the mouse on everything, before enabling the mouse on the one parent element, just to make certain.

[Duugu]

Originally Posted by Seerah I'm not sure if a frame's being mouse enabled is inheritable...

It is inheritable. But the attributes are inherited only once (frame creation) - not at runtime. Setting a attribute at runtime won't affect the child frames.

Imho you'll have to iterate over all the child frames.