WoW BlueTracker: You killed $parent?

WoW Blue Tracker	Home \| RSS \| News \| Contact Recent \| Search \| Archive \| CS Posts

Poster: Tohopka at 7/12/2005 4:50:00 PM PDT Subject: You killed $parent?
	In every instance of $parent where the frame (buttons are fine) inherits another frame, $parent will now return UIParent instead of the true parent frame. I've seen a few AddOns do this now. The breakages after patches are becoming a little ridiculous. One wonders if Blizzard even uses that test server or whether it's just faux. "You are one with the pootworm. REJOICE!"
	http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=178953&p=#post178953

Poster: slouken at 7/12/2005 4:57:06 PM PDT Subject: Re: You killed $parent?
	Can you post a minimal example that has this problem? The default UI uses $parent quite a bit, and doesn't have any problems.
	http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=178953&p=#post178956
Poster: slouken at 7/12/2005 5:37:40 PM PDT Subject: Re: You killed $parent?
	Q u o t e: <Frame name="AceGUIBorderFrameTemplate" parent="UIParent" virtual="true"> This is key here. The code was changed to allow virtual frames to define a parent. You've defined the parent to be UIParent. So... when $parent is evaluated, you're actually getting UIParent in the name.
	http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=178953&p=#post178993

WoW Blue Tracker: Archiving World of Warcraft Blue Posts since March 2005	Home \| RSS \| News \| Contact Recent \| Search \| Archive \| CS Posts

Why Ads?