On 28 November 2012 17:42, Alex Harui wrote:
> modify DG to dispatch such an event.
> Another is to provide an alternate item editor that dispatches the event
> from the DG in its save() method.
>
> In the new framework I am rewriting, I would argue for the second option.
> The DG should not was
On 11/28/12 8:58 AM, "João Fernandes"
wrote:
> Carol but that's the point, with mx:datagrid you can prevent any save()
> using an event listener and without extending the default itemEditor by
> listening to the session_edit_end and calling preventDefault on the event
> dispatched. With spark
Carol but that's the point, with mx:datagrid you can prevent any save()
using an event listener and without extending the default itemEditor by
listening to the session_edit_end and calling preventDefault on the event
dispatched. With spark Datagrid it's not possible. It doesn't make sense
for each
I think you override IGridItemEditor save() to do what you want.
Carol
On 11/28/12 11 :29AM, "João Fernandes"
wrote:
>Carol, with mx:Datagrid you can prevent a edit session from ending by
>calling preventDefault on sessionEditEnd event. There is no way to achieve
>the same with the spark datagr
Carol, with mx:Datagrid you can prevent a edit session from ending by
calling preventDefault on sessionEditEnd event. There is no way to achieve
the same with the spark datagrid. Being able to capture the sessionEditEnd
allow me to use a generic item editor and instead of implementing
validate() in
I'm not quite sure what you are trying to do but I bet you can currently
do it with the existing Spark DataGrid. You may have to do it
differently. Have you looked at [1]? Would it be possible to provide a
small example?
Carol
[1]
http://help.adobe.com/en_US/flex/using/WS0ab2a460655f2dc3-427f
