Every example out there should be doing this.  Look at the source for
mx.controls.listClasses.TileListItemRenderer.  You can also find
examples on my blog (blogs.adobe.com/aharui)

________________________________

From: [email protected] [mailto:[EMAIL PROTECTED] On
Behalf Of Wayne LaRochelle
Sent: Thursday, September 27, 2007 3:05 PM
To: [email protected]
Subject: Re: [flexcoders] DataGrid cell access question



HI!!

thanks for responding.

I'm confused about the use of the data property can you aim me in a
direction of an example???

Thanks







----- Original Message ----
From: Alex Harui <[EMAIL PROTECTED]>
To: [email protected]
Sent: Thursday, September 27, 2007 12:55:12 PM
Subject: RE: [flexcoders] DataGrid cell access question



renderers are data driven.  The .data property should hold the items
from the XML file and you should set the buttons and textArea based on
what you find in the .data property.

________________________________

From: [EMAIL PROTECTED] ups.com [mailto:flexcoders@ yahoogroups. com]
On Behalf Of waynelll
Sent: Thursday, September 27, 2007 11:42 AM
To: [EMAIL PROTECTED] ups.com
Subject: [flexcoders] DataGrid cell access question



HI!!

I have a question about using a DataGrid with a custom itemRender. 

Each of my DataGrid Cells contains an HBox within which are 2 buttons
and a text field. I realize that there are performance issues with
this design but these are my current specs.

The problem I am having is how to initialize the two buttons and the
text area at startup. Each button can be in one of four states and the
text area can contain any number between 1 and 100, the info comes out
of a XML file which I read in at startup.

I have been unsuccessful in trying to walk through the DataGrid using 
getChildAt to gain access to the Cell and Buttons.

I'm looking for any ideas. 

WAYNELLL





________________________________

Yahoo! oneSearch: Finally, mobile search that gives answers
<http://us.rd.yahoo.com/evt=48252/*http://mobile.yahoo.com/mobileweb/one
search?refer=1ONXIC> , not web links. 

 

Reply via email to