Comments on: Accessing a List from its itemRenderer http://joelhooks.com/2008/03/18/accessing-a-list-from-its-itemrenderer/ even if you aren't testing your code, you should write testable code Sat, 04 Sep 2010 16:45:41 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Paul http://joelhooks.com/2008/03/18/accessing-a-list-from-its-itemrenderer/comment-page-1/#comment-45 Paul Thu, 15 May 2008 13:37:00 +0000 http://joelhooks.com/2008/03/18/accessing-a-list-from-its-itemrenderer/#comment-45 thanks so much for posting this, you concisely made clear what the Flex manual fails to, helped me a lot thanks so much for posting this, you concisely made clear what the Flex manual fails to, helped me a lot

]]> By: Brixel http://joelhooks.com/2008/03/18/accessing-a-list-from-its-itemrenderer/comment-page-1/#comment-44 Brixel Thu, 10 Apr 2008 19:17:32 +0000 http://joelhooks.com/2008/03/18/accessing-a-list-from-its-itemrenderer/#comment-44 Hello there. I've been searching for a solution to a similar problem. I have a custom MXML component, which is a tree. It has some public properties in it, etc. It points to an AS class as it's itemRenderer. What is escaping me is the ability to target the public properties of that component from with in the AS class. I can get to the instance of the tree, but not the stuff inside the component container itself. Now calling something like "document.myCustomTreeComponent.myPublicProperty" will work, but I shouldn't have to go all the way out and back in just to get what should be in my "parent" container, should I? Hoping for any help, thanks. Hello there. I’ve been searching for a solution to a similar problem. I have a custom MXML component, which is a tree. It has some public properties in it, etc. It points to an AS class as it’s itemRenderer.

What is escaping me is the ability to target the public properties of that component from with in the AS class. I can get to the instance of the tree, but not the stuff inside the component container itself.

Now calling something like “document.myCustomTreeComponent.myPublicProperty” will work, but I shouldn’t have to go all the way out and back in just to get what should be in my “parent” container, should I?

Hoping for any help, thanks.

]]>