I've done something like this before, where fullField is the String
representation of the field (like field1.field2.field3) and item is the
top-level data object:

var split:Array = fullField.split(".");

var valueObj:Object = item;
for(var i:int=0; i<split.length; i++) {
    valueObj = valueObj[split[i]];
}


On Tue, Jun 10, 2008 at 9:30 PM, Alex Harui <[EMAIL PROTECTED]> wrote:

>    There's a DeepDataGridColumn example on my blog that can do simple
> field.subfield
>
>
>  ------------------------------
>
> *From:* flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] *On
> Behalf Of *ben.clinkinbeard
> *Sent:* Tuesday, June 10, 2008 7:50 PM
> *To:* flexcoders@yahoogroups.com
> *Subject:* [flexcoders] Re: Any best-practice for
> labelField="field.innerField" on things like DataGridC
>
>
>
> I don't think you can do field.subField but you could use
> labelFunctions to accomplish essentially the same thing. Heck, you
> might even be able to set dataField = "field.subField" and then use a
> generic labelFunction that does something like return
> data[column.dataField]. Just a guess on that part but labelFunction is
> definitely the core of what you'll need.
>
> HTH,
> Ben
>
> --- In flexcoders@yahoogroups.com <flexcoders%40yahoogroups.com>, "Josh
> McDonald" <[EMAIL PROTECTED]> wrote:
> >
> > Hey guys,
> > Is there a well-used trick to reference "field.subField" rather than
> just
> > "field" when setting up datagrid columns? I'd rather not have to
> flatten my
> > DTOs or add a bunch of redundant get functions if possible - the DTO is
> > bindable and the fields are just public vars.
> >
> > Cheers,
> > -Josh
> >
> > --
> > "Therefore, send not to know For whom the bell tolls. It tolls for
> thee."
> >
> > :: Josh 'G-Funk' McDonald
> > :: 0437 221 380 :: [EMAIL PROTECTED]
> >
>
>  
>

Reply via email to