Looks like we cannot reproduce this. Please provide another test case to reproduce this issue.
  1. #1
    Sencha User
    Join Date
    Dec 2012
    Posts
    13
    Vote Rating
    1
    artsiom_aliakseyenka is on a distinguished road

      0  

    Default loadMoreCmp is not destroyed, when list is destroyed

    loadMoreCmp is not destroyed, when list is destroyed


    REQUIRED INFORMATION

    Ext version tested:
    • Sencha Touch 2.1
    Browser versions tested against:
    • Chrome 23(Windows)
    Description:
    • Ext.plugin.ListPaging contains loadMoreCmp.
    • This component is not destroyed, when parent list is destoyed
    Steps to reproduce the problem:
    • Create List with plugin Ext.plugin.ListPaging.
    • Several times scroll down to allow list to load more results.
    • Destroy List and check Ext.ComponentManager.map, you will find there loadMoreCmp component, although list was already destroyed.
    The result that was expected:
    • Ext.plugin.ListPaging should destroy loadMoreCmp component
    The result that occurs instead:
    • loadMoreCmp is not destroyed when list is destroyed
    Test Case:


    Code:
            Ext.application({
                name: 'MyApp',
                list: null,
                launch: function () {
    
    
                    this.list = Ext.create('Ext.dataview.List', {
                        fullscreen: true,
                        data: [
                            { title: 'Item 1' },
                            { title: 'Item 2' },
                            { title: 'Item 3' },
                            { title: 'Item 4' }
                        ],
    
    
                        plugins: [
                            {
                                xclass: 'Ext.plugin.ListPaging',
                                autoPaging: true
                            }
                        ],
    
    
                        itemTpl: ['{title}']
                    });
                      //scroll down several times to allow plugin to load more results.
                     //call MyApp.app.list.destroy().
                     // Check Ext.ComponentManager.map and you'll  find not destroyed  loadMore component
                }
             });

  2. #2
    Sencha - Senior Forum Manager mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Location
    Gainesville, FL
    Posts
    35,704
    Vote Rating
    751
    mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute

      0  

    Default


    It looks like it is destroyed to me:

    Code:
    Ext.create('Ext.dataview.List', {
        fullscreen : true,
        data       : [
            { title : 'Item 1' },
            { title : 'Item 2' },
            { title : 'Item 3' },
            { title : 'Item 4' }
        ],
    
        plugins : [
            {
                xclass     : 'Ext.plugin.ListPaging',
                autoPaging : true
            }
        ],
    
        itemTpl : '{title}',
        items   : [
            {
                xtype   : 'button',
                docked  : 'top',
                ui      : 'decline',
                handler : function(btn) {
                    var list        = btn.up('list'),
                        plugins     = list.getPlugins(),
                        plugin      = plugins[0],
                        loadMoreCmp = plugin.getLoadMoreCmp(),
                        id          = loadMoreCmp.getId(); //ext-component-3 for my test
    
                    list.destroy();
    
                    if (Ext.ComponentManager.map.hasOwnProperty(id)) {
                        console.warn('loadMoreCmp not destroyed!');
                    } else {
                        console.log('loadMoreCmp has been destroyed!'); //this gets logged
                    }
    
                    console.log(Ext.ComponentManager.map);
                }
            }
        ]
    });
    Mitchell Simoens @SenchaMitch
    Sencha Inc, Senior Forum Manager
    ________________
    Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
    https://github.com/mitchellsimoens

    Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/

    Need more help with your app? Hire Sencha Services services@sencha.com

    Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is in print!

    When posting code, please use BBCode's CODE tags.

  3. #3
    Sencha User
    Join Date
    Dec 2012
    Posts
    13
    Vote Rating
    1
    artsiom_aliakseyenka is on a distinguished road

      0  

    Default


    Mitchell,
    I tested your code also, the component is not destroyed. As i wrote in steps: "Several times scroll down to allow list to load more results." If you do one load of data, component is destroyed. If i do several load, to allow list's height to be bigger than screen's height, then component is not destroyed.
    I noticed, that component is sometimes destroyed. May be reason is in scrollable component.

  4. #4
    Sencha User
    Join Date
    Dec 2012
    Posts
    13
    Vote Rating
    1
    artsiom_aliakseyenka is on a distinguished road

      0  

    Default


    Hi Mitchell,
    Please see attached video. I used your sources above and reproduced this bug.

Thread Participants: 1

film izle

hd film izle

film sitesi

takipci kazanma sitesi

takipci kazanma sitesi

güzel olan herşey

takipci alma sitesi

komik eğlenceli videolar