Re: [flexcoders] Re: ItemEditor | Multiple Components | Focus Issue

2010-07-23 Thread Alex Harui
Looks like there’s a bug in the DG editing code. Please open a bug with a test case. Try not calling event.preventDefault (but still call destroyItemEditor). On 7/22/10 8:18 AM, Rajan ilikef...@yahoo.com wrote: I looked at your sample but it does not contain nested properties.So

[flexcoders] Re: ItemEditor | Multiple Components | Focus Issue

2010-07-22 Thread Rajan
No, i have not borrowed the code for popup editorut yes i am using the popup editor. Please see the code for Pop up at http://ilikeflex.blogspot.com/ http://ilikeflex.blogspot.com/ Under 'Code for PopUp' But my itemEditEnd event handler code is below. private function

Re: [flexcoders] Re: ItemEditor | Multiple Components | Focus Issue

2010-07-22 Thread Alex Harui
You might want to compare the popup editor example from my blog with your example On 7/22/10 6:59 AM, Rajan ilikef...@yahoo.com wrote: No, i have not borrowed the code for popup editorut yes i am using the popup editor. Please see the code for Pop up at http://ilikeflex.blogspot.com/

[flexcoders] Re: ItemEditor | Multiple Components | Focus Issue

2010-07-22 Thread Rajan
I looked at your sample but it does not contain nested properties.So event.preventDefault(); is not required and everything works fine. --- In flexcoders@yahoogroups.com, Alex Harui aha...@... wrote: You might want to compare the popup editor example from my blog with your example On

[flexcoders] Re: ItemEditor | Multiple Components | Focus Issue

2010-07-21 Thread Rajan
I have put the following code in the datagrid and found that couple of times 'itemEditorInstance' is null.So the focus does not move ahead. Any pointer.. override protected function keyDownHandler(event:KeyboardEvent):void { // this is technically illegal, but works

Re: [flexcoders] Re: ItemEditor | Multiple Components | Focus Issue

2010-07-21 Thread Alex Harui
The focusIn handler would tell you more. Make sure you examine/display the event.target and event.relatedObject. Maybe the parent/owner chain in your editor isn’t set up. On 7/20/10 11:41 PM, Rajan ilikef...@yahoo.com wrote: I have put the following code in the datagrid and found that

[flexcoders] Re: ItemEditor | Multiple Components | Focus Issue

2010-07-21 Thread Rajan
Hi I have created simple test case to identify the issue. If i remove itemEditEnd then i have no issues with the focus. It works cleanly and focus moves from one column to another. But if add itemEditEnd then focus does not move from 1st column to 2 nd column. So event.preventDefault();

[flexcoders] Re: ItemEditor | Multiple Components | Focus Issue

2010-07-21 Thread Rajan
Actually itemEditEnd in the real sceanrio looks like below. Since i am uisng the nested datafield i am calling the event.preventDefault(); datGrid.destroyItemEditor(); datGrid.dataProvider.itemUpdated(event.itemRenderer.data); So my dataprovider gets updated with the new value when i use the

Re: [flexcoders] Re: ItemEditor | Multiple Components | Focus Issue

2010-07-21 Thread Alex Harui
I noticed your editor looks like it is a popup. Have you borrowed the code from the popup editor example as well? On 7/21/10 11:43 AM, Rajan ilikef...@yahoo.com wrote: Actually itemEditEnd in the real sceanrio looks like below. Since i am uisng the nested datafield i am calling the

[flexcoders] Re: ItemEditor | Multiple Components | Focus Issue

2010-07-20 Thread Rajan
Actually, i have same itemeditor in different columns. Column1 1.One Tab - focus on textinput 2.Second Tab - focus on image. 3.Third Tab - Don't know where does the focus goes. Column2 4.Fourth Tab - focus on textinput 5.Fifth Tab - focus on image. I want to fix that on third tab it show go

Re: [flexcoders] Re: ItemEditor | Multiple Components | Focus Issue

2010-07-20 Thread Alex Harui
Add a focusIn handler on the app that displays the event.target and event.relatedObject. Maybe that will generate some clues. On 7/20/10 10:25 AM, Rajan ilikef...@yahoo.com wrote: Actually, i have same itemeditor in different columns. Column1 1.One Tab - focus on textinput 2.Second Tab