On 5/14/13 10:29 PM, "Justin Mclean" <jus...@classsoftware.com> wrote:
> Hi,
>
>> I looked at FLEX-16857, and IMO, it is not a bug. The code is not calling
>> refresh after setting sort = null and before adding items. I haven't tried
>> it, but I suspect that would avoid the error.
> That is broken as well the objects are still sorted rather than reverting to
> their original order.
That's odd. I would certainly expect more bugs filed if you couldn't undo a
sort.
>
>> When theGridItemEditor goes to save the new data, the editor saves any
>> current sort,
>> sets sort = null, then saves the new, then restores the sort and does not
>> call refresh().
> Ouch. Why does it need to do that it should be able to save the new data
> directly.
IIRC, if you have an MX DG sorted by first name and you change Alex to Zlex,
depending on what you do next, the DG scrolls to the bottom to show its new
position, or when you click on the row below the edited row disappears and
the row you clicked on jumps up. I think they are trying to avoid that in
Spark DG.
>
>> 1) verify that refresh() avoids the RTE in FLEX-16857, revert this change
>> and maybe update the doc
> There no RTE but the list is not left in the correct state. I assume this may
> cause further issues down the track, probably need to fix this as well.
>
>> 2) change the behavior of Spark DG when you edit an item in the sort column.
> I'd for this option but no idea how easy/hard it it right this second.
I would just take the sort-saving logic out. I'll try it and see if other
tests then start to fail.
>
> Thanks,
> Justin
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
