Comments on: Spark equivalent of DisplayObjectContainer.contains() http://flexponential.com/2009/12/01/spark-equivalent-of-displayobjectcontainer-contains/ Programming under the influence of Flex Sun, 22 Jan 2012 01:08:12 +0000 hourly 1 http://wordpress.org/?v=3.3 By: Ali http://flexponential.com/2009/12/01/spark-equivalent-of-displayobjectcontainer-contains/comment-page-1/#comment-222 Ali Fri, 04 Dec 2009 10:17:52 +0000 http://flexponential.com/?p=255#comment-222 Thx for the Tip :) Thx for the Tip :)

]]> By: Steven Shongrunden http://flexponential.com/2009/12/01/spark-equivalent-of-displayobjectcontainer-contains/comment-page-1/#comment-214 Steven Shongrunden Wed, 02 Dec 2009 06:30:45 +0000 http://flexponential.com/?p=255#comment-214 <a href="#comment-212" rel="nofollow">@Tink </a> - You're right that was poorly worded. I updated it to read "because not every element in a spark container is a DisplayObject". Thanks for pointing that out. One of these days I'll get around to writing a post on an explanation of DisplayObject sharing in spark containers. @Tink – You’re right that was poorly worded. I updated it to read “because not every element in a spark container is a DisplayObject”. Thanks for pointing that out. One of these days I’ll get around to writing a post on an explanation of DisplayObject sharing in spark containers.

]]> By: Tink http://flexponential.com/2009/12/01/spark-equivalent-of-displayobjectcontainer-contains/comment-page-1/#comment-212 Tink Tue, 01 Dec 2009 13:22:13 +0000 http://flexponential.com/?p=255#comment-212 "because not every child of a spark container is a DisplayObject." That line could be a little confusing for people. If its a child it has to be a DisplayObject. You talking specifically about visual elements, which cannot be a child, the child is its owner, where the info stored inside the element is actually drawn and displayed. I agree though that the API for elements seems somewhat incomplete due to an extremely easy method that could be implements by Adobe. “because not every child of a spark container is a DisplayObject.”

That line could be a little confusing for people. If its a child it has to be a DisplayObject. You talking specifically about visual elements, which cannot be a child, the child is its owner, where the info stored inside the element is actually drawn and displayed.

I agree though that the API for elements seems somewhat incomplete due to an extremely easy method that could be implements by Adobe.

]]>