Ok.. figured it out. The issue was my data.  I had rows where the level was 0 (root) but they also had a parent ids that didn't exist in the row set.  So if anyone sees their columns get wacky on a column sort this could be your issue.  I don't see this as a "bug" but it probably wouldn't hurt to override the parent id to "NULL" on any root rows before the processing of the table data starts.. but obviously I am not the expert on the logic in the treegrid so there could be a good reason not to do this.

-Doug

Hello,

After doing some more testing it seems that when I just return the level 0 nodes the sorting issues go away.  Are there requirements in how the xml nodes should be ordered? For example, do the level 1 nodes need to be right after their parent (level 0) node in the xml?

Thanks,

Doug 

Hello,

I have been working with your amazing plug-in and trying to use the treegrid functionality.  I have been able to load a grid using xml and the adjacency model (loading all the nodes at once) but when I try to sort using one of the column headers I get some strange behavior.  It seems the columns change to be about equal width but the headers don't change so the vertical alignment gets really off.  I also notice that there does seem to be some local sorting going on.. but not on all the level 0 nodes are sorted ( I am guessing those are the only ones that would get sorted).  The same behavior happens in IE 8 and FF 3.5.4. and I have tried jqGrid 3.5 and 3.6 .  The only big differences I can see between the demo on your site and my grid is that I am using the xmlmap parameter (instead of each element being ”cell”) and it looks like the demo uses the Nested Set Model (the default).  Any ideas?

Thanks for any help,   

Doug