Dataview and Store Filtering

[Pandorian]

REQUIRED INFORMATION

Ext version tested:

• Touch 2.0.1rc

Browser versions tested against:

• Chrome 20 (Win7)
• Safari iOS 5.1

DOCTYPE tested against:

• HTML5

Description:

After applying a filter to a store linked to a dataview, the dataview seems to reference the old record data when this.getRecord() is used.

Steps to reproduce the problem:

The attached app was generated with Sencha Command, but does not include the SDK folder.

Lauch the App
Click on the Show button on the 2nd line - it will alert "Cat 1 Sub cat 1".
Click on the Expand button on first line - the 3 "Cat 1 sub cat 1/2/3" entries will be hidden.
Click on the Show button on the 2nd line - it will alert "Cat 1 Sub cat 1".


The result that was expected:

An Alert showing "Category 1"

The result that occurs instead:

An Alert showing "Cat 1 Sub cat 1"

Test Case:

See attached App

HELPFUL INFORMATION


Screenshot or Video:

• attached

[mitchellsimoens]

Thanks for the report.

Can we get the app.css so that the expand/show are lined up correctly so when the dev that gets this ticket can easily see which button is which?

[Pandorian]

Sure - here you go.

There are no changes from the one produced from the sencha generate command.

[Pandorian]

Is there any news on this bug - it is now causing me some pain as I cannot complete my development.

Thanks.

[TommyMaintz]

Hi Pandorian,

Sorry for the big delay. I hope this might still help you get passed this issue. I think the following override will fix the problem.

Ext.define('Ext.dataview.component.ContainerFix', {
    override: 'Ext.dataview.component.Container',
    
    updateListItem: function(record, item) {
        if (item.updateRecord) {
            if (item.getRecord() === record) {
                item.updateRecord(record);
            } else {
                item.setRecord(record);
            }
        }
    }
});

This will also be fixed in the next 2.1 release.

Best,
Tommy

[Pandorian]

Hi Tommy,

Thank for the fix, but alas it is too late for me. I struggled for a number of months battling bugs, inconsistencies and other issues in the framework, that I have abandoned Sencha Touch and I am now actively re-writing it as a native application in Objective-C.

Regards