NestedList NodeInterface insertChild does not display in correct order in List

[drb]

REQUIRED INFORMATION
Ext version tested:

• Sencha Touch 2.0.1.1

Browser versions tested against:

• Chrome 21.0.1180.75 m

DOCTYPE tested against:

• html

Description:

• In Touch 2.0.1.1 (and 2.0), inserting an item does insert it into the children, but the inserted item is displayed at the end of the List.

Steps to reproduce the problem:

• Run the code below.
• Tap on Drinks, then Water, then any row
• The Insert row should be in front of the row just tapped, but it is as the end.
• Back all the way back to Groceries and then forward again to Waters and you will see that it is now in the correct position. This is because there are only 2 Lists in a NestedList and the List has been refreshed, showing the actual position from the node's children.

Ext.setup({
    onReady: function () {

        var data = {
            text: 'Groceries',
            items: [{
                text: 'Drinks',
                items: [{
                    text: 'Water',
                    items: [{
                        text: 'Sparkling',
                        leaf: true
                    }, {
                        text: 'Still',
                        leaf: true
                    }, {
                        text: 'Deep',
                        leaf: true
                    }, {
                        text: 'Muddy',
                        leaf: true
                    }]
                }]
            }]
        };

        Ext.define('ListItem', {
            extend: 'Ext.data.Model',
            config: {
                fields: [{
                    name: 'text',
                    type: 'string'
                }]
            }
        });

        var store = Ext.create('Ext.data.TreeStore', {
            model: 'ListItem',
            defaultRootProperty: 'items',
            root: data
        });

        var nestedList = Ext.create('Ext.NestedList', {
            fullscreen: true,
            title: 'Groceries',
            displayField: 'text',
            store: store,
            listeners: {
                leafitemtap: function (nlist, list, index, element, record, e, opts) {
                    console.log(record.get("text"));
                    //record.parentNode.appendChild({ "text": "Added", "leaf": true });
                    record.parentNode.insertChild(index, { "text": "Inserted", "leaf": true });
                    if (false) {
                        // should work but does not
                        list.getStore().sort([{ "property": "text", "direction": "ASC"}]);
                    }
                    if (false) {
                        // Does work
                        record.parentNode.sort(function (rec1, rec2) {
                            var val1 = rec1.get("text");
                            var val2 = rec2.get("text");
                            if (val1 > val2) { return 1; }
                            if (val1 = val2) { return 0; }
                            return -1;
                        }, false, false);
                    }
                    if (false) {
                        // Also should work but does not
                        record.parentNode.sort([{ "property": "text", "direction": "ASC"}]);
                    }
                }
            }

        });
    }
});

HELPFUL INFORMATION
Screenshot or Video:

• none

See this URL for live test case: none

Debugging already done:

• none

Possible fix:

• not provided

Additional CSS used:

• only defaults .css

Operating System:

• Windows 7

[Jamie Avins]

Thank you for the report. This may have been fixed in a patch version, we'll verify and get back to you.

[Jamie Avins]

Scenario 1: Since NestedList uses a TreeStore, you would need to sort the nlist in your example instead of the list.

Scenario 2: This works here because you are calling the nodeInterface's sort method directly and use a sortFn.

Scenario 3: This doesn't work because nodeInterface's sort method doesn't currently accept that syntax.

We're looking into what can be done to help make this easier in the future. Note that much of the reasoning behind how it works now is we don't have a very good way to determine if the call to sort is coming from an internal method (the TreeStore) or a developer call (just a NodeInterface). This can lead to recursion problems in the current implementation and it's why we have some of the limitations.

[drb]

Jamie,
Can you move the comment to the right bug?
Thanks David

[drb]

Thanks
David

[TommyMaintz]

I'm pretty sure this issue has been fixed as part of a previous release. The testcases we have for this issue (which is based on your provided testcase) runs correctly in the 2.2 codebase for me.

Please let me know if anyone still has this issue or something related to it and I will reopen.

Best,
Tommy