Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    ListGrid Multiple Sort problem

    Hello,

    SmartClient version 8.0 (evaluation version)
    Internet Explorer

    I'm testing out the multiple sort in the ListGrid.
    While testing the multiple sort, there is a problem : not all the values of the "initialSort" properties are taken into account.
    In the following example, the "ascending" sort on the "d" column is not taken into account.
    The test can be made in the demo feature "http://www.smartclient.com/#multiLevelSortLG". You can see that the arrow on the "d" column is indicated as "descending".

    Code:
    isc.ListGrid.create({
        top: 30, width:700, height:300, 
        alternateRecordStyles:true,
        canMultiSort: true,
        fields:[
          {name: "a",title: "A",width: "17%"},
          {name: "b",title: "B",width: "18%"},
          {name: "c",title: "C",width: "20%"},
          {name: "d",title: "D",width: "15%"},
          {name: "e",title: "E",width: "30%"}
        ],
    	initialSort: [
          {property: "d", direction: "ascending"},
          {property: "a", direction: "descending"}
        ]
    })
    If data is added, the sort on the "d" column is performed correctly but the "d" column is still indicated as descending sort.
    Code:
    isc.ListGrid.create({
        top: 30, width:700, height:300, 
        alternateRecordStyles:true,
        canMultiSort: true,
        fields:[
          {name: "a",title: "A",width: "17%"},
          {name: "b",title: "B",width: "18%"},
          {name: "c",title: "C",width: "20%"},
          {name: "dodo",title: "D",width: "15%"},
          {name: "e",title: "E",width: "30%"}
        ],
    data :[
    { "dodo": "ta", "a" :" y" }
    ,{ "dodo": "aa", "a" :" z" }
    ],
        initialSort: [
          {property: "dodo", direction: "ascending"},
          {property: "a", direction: "descending"}
        ]
    })
    Thank you

    #2
    Hi Gli
    Thanks for letting us know.
    We have resolved the problem in our mainline codebase - the fix will appear in builds from this point forward.

    Comment

    Working...
    X