In porting to smartGWT 13.0 from 12.1 I had an issue where an exception caused a TreeGrid to be drawn in the upper left rather then placed in it's layout. The cause was saving a 13.0 version of the viewstate and using it with currently deployed 12.1 software. I noticed 3 new TreeGrid viewstate keys that were added in 13.o, where the hilite key was the root cause. If able, it would be nice to see the 13.0 viewstate being compatible with 12.1.
new keys:
"sort":"[No Sorting]", "hilite":"[No Hilites]", "group":"[No Grouping]", "showFilterEditor":false
Note: our implementation does some view state converting between String, map, and javascript object in the process of storing/retrieving from the DB so you may not see this with you save/restore API directly. The "[No Hilites]" string obviously would not convert well to an array, even if just to later be converted back to a string.
Thanks
new keys:
"sort":"[No Sorting]", "hilite":"[No Hilites]", "group":"[No Grouping]", "showFilterEditor":false
Note: our implementation does some view state converting between String, map, and javascript object in the process of storing/retrieving from the DB so you may not see this with you save/restore API directly. The "[No Hilites]" string obviously would not convert well to an array, even if just to later be converted back to a string.
Thanks
Comment