OK, debugged into it. There is two, so I'd say it is a bug. Way back in May I added code to GridItemEditor.save() to force focus back to the DG so that controls commit their values. I thought there was a check to prevent save() from doing its work twice, but there isn't. Another event gets dispatched (in my case from hitting the ENTER key to close the editor).
Seems like we need a flag to determine that save has done its thing. -Alex On 11/7/13 7:12 PM, "Paul Hastings" <[email protected]> wrote: >On 11/8/2013 6:09 AM, Alex Harui wrote: >> Is it the same event instance? Otherwise, try following the code back >>to > >i believe so. > >something i forgot to mention that this is a spark datagrid (i guess i >should >compare w/mx datagrid to see what's what). > >i've isolated the datagrid off on its own to isolate from potential >issues >w/module, remoting, etc. still shows the issue: > >https://dl.dropboxusercontent.com/u/130830/flex/gridEvent.html > >click "edit" to start editing, edit the "edit data" column. every time >that >column is updated, two GridItemEditorEvent.GRID_ITEM_EDITOR_SESSION_SAVE >events >are fired off. same target, event phase, row, column. > >source for that is: > >https://dl.dropboxusercontent.com/u/130830/flex/gridEvent.zip > >i think this is the first time we've used in-line datagrid editing like >this, so >maybe we're doing it wrong? but it follows the examples i've dug up & i >*think* >i gave a grasp of the basic concepts (famous last words). > >thanks. > > > > > >
