Hidden ScrollChild elements Clickable

[Mayron]

I've noticed that interactive elements attached to a frame being used as a scroll child for a ScrollFrame are still usable despite being scrolled out of view. I've noticed that Blizzard GUI panels don't have this problem and not sure why. I can't seem to figure it out.

I've tried "IsMouseOver" and "IsVisible" but anything on the scroll child frame, even if out of view, will return true.

Here is what I mean:



However, the bottom half of this Blizzard Button cannot be clicked on if it is out of view which is what I want to do with my frames:



Does anyone know why this might be?
Thank you

[jeruku]

This was solved over on this thread.

Originally Posted by MunkDev Not sure if I'm providing any new information here, but I encountered this as well. The issue was of course the change to scroll frames, as they will not clip their children automatically unless defined either in XML or lua. To solve this, I simply put this in my scroll frame wrapper: frame:SetClipsChildren(true) In XML, the tag is clipChildren="true". This causes any children outside the boundaries of the frame to be unclickable and frankly not drawn at all. Any scroll frame now also returns an object type of plain "Frame", suggesting that the specific "ScrollFrame" widget doesn't exist anymore and is now an intrinsic frame template that simply provides scrolling and child anchoring methods.

[Mayron]

Excellent thank you! I reply on wowprogramming which always seems out dated and I never know how to find new API listings. It seems like such a stupid change as this should be enabled by default :/

[Mayron]

The only problem with this is that it hides the scroll bar as the scroll bar is positioned outside of the scroll frame and needs to be a child for the OnVerticalScroll event to work. It also clips the border from showing. Very frustrating and restrictive :/

[Zadrax]

Sorry for bumping an old thread. The solution is to use frame:SetToplevel(true) and avoid using scrollframe:SetClipsChildren(true). This has caused me quite a bit of trouble, so I'm noting it here for posterity.