My advice also. I only use the built-in editing functionality for simple drop-in renderers. For any ting more complex, I handle the dataProvider updating myself.
Tracy Spratt, Lariat Services, development services available _____ From: [email protected] [mailto:[email protected]] On Behalf Of Gregor Kiddie Sent: Friday, July 31, 2009 3:20 AM To: [email protected] Subject: RE: [flexcoders] ItemRenderer that switches to edit mode depending on where it's clicked Honestly? I'd take a leaf out of Flex 4, and ignore the ItemEditor. You can get the same effect by having the item renderer switch to an editable state, and therefore get the functionality you want without having to wade through the ItemEditor nonsense. Gk. Gregor Kiddie Senior Developer INPS Tel: 01382 564343 Registered address: The Bread Factory, 1a Broughton Street, London SW8 3QJ Registered Number: 1788577 Registered in the UK Visit our Internet Web site at <blocked::http://www.inps.co.uk/> www.inps.co.uk The information in this internet email is confidential and is intended solely for the addressee. Access, copying or re-use of information in it by anyone else is not authorised. Any views or opinions presented are solely those of the author and do not necessarily represent those of INPS or any of its affiliates. If you are not the intended recipient please contact [email protected] _____ From: [email protected] [mailto:[email protected]] On Behalf Of hr1ny Sent: 30 July 2009 18:05 To: [email protected] Subject: [flexcoders] ItemRenderer that switches to edit mode depending on where it's clicked I'm trying to create a List with an ItemRenderer that switches to an ItemEditor depending on where in the ItemRenderer (what subcomponent) is clicked, but I'm not sure how to do this. Essentially, I'd like to go into edit mode if user clicks on a data field, but to do nothing (other than select the item) if user clicks elsewhere in the item. (Imagine that the ItemRenderer contains some icons, buttons, and empty space as well as data fields). I would think that the trick is to use the itemEditBeginning event handler (and in certain cases call event.preventDefault()), but this event does not know about subcomponents of the ItemRenderer, and subcomponents of the itemRenderer don't know about this event. --Henry
