Question one: I would approach this a little differently Rather than attempting to create a double-binding mechanism. Take advantage of the ModelLocator, and rework the target of the data update from the datagrid. The ItemEditor or after edit event should update the ModelLocator directly, rather than attempting to update the bound data item in the datagrid, this should automatically push the updated value back into the datagrid, giving the impression that it was updated directly in the datagrid. ModelLocator - Send out Data to bound locations - Receive updated data Data Display Item - Bind to ModelLocator - Update ModelLocator with new data Regarding Question two: A command could quite easily perform the item selection after the data update had been retrieved and correctly assigned to the ModelLocator Hope this helps you some. Graham Weldon Larry Liang wrote:
__._,_.___ -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
SPONSORED LINKS
YAHOO! GROUPS LINKS
|
- [flexcoders] two direction binding and cairngorm Larry Liang
- [flexcoders] Runtime code evaluation Damien Mandrioli
- RE: [flexcoders] Runtime code evaluation Gordon Smith
- RE: [flexcoders] Runtime code evaluation Damien Mandrioli
- Re: [flexcoders] Runtime code evaluat... Anatole Tartakovsky
- Re: [flexcoders] two direction binding and cairng... Graham Weldon