On 6/2/14 7:38 AM, "Michael A. Labriola" <labri...@digitalprimates.net> wrote:
>>It's a valid question. There is probably no one right answer. My >>answer is that, if you didn't intend the compareFunction to use the >>field name in the SortField, why use a SortField at all? Why not just >>use the top-level Sort compareFunction. > >Just continuing the discussion. I think the case here is that you have >(n) fields but only one of them needed a compareFuntion. This is often >the case in DataGrids where you have a bunch of standard columns that map >to an object in the dataprovider and one that is derived. A totally reasonable scenario. It is tempting to simply remove this check, but you never know when someone is relying on this behavior. -Alex
