PDA

View Full Version : [FIXED127] List/NestedList disabled/setDisabled not working



tfrugia
19 Jul 2010, 8:41 AM
Setting the disabled property or using setDisabled(true) seems to have no affect on lists and nested lists.

aconran
6 Sep 2010, 12:15 PM
Thanks for reporting this bug. Disabling a List/NestedList will be fixed in the next build (after 0.94).

aconran
9 Sep 2010, 1:40 PM
Fixed in 0.95.

Old McStopher
20 Jul 2011, 8:08 AM
I still seem to be having this issue in 1.1.0. I can disable the panel that contains the list. I can also hide the list. But I cannot disable the list itself. See comments in code...



myApp.views.PResultsList = Ext.extend(Ext.Panel, {

dockedItems: [{
id: 'search',
xtype: 'toolbar',
items: {
xtype: 'searchfield',
placeHolder: 'Search',
name: 'searchfield',
listeners: {
focus: function() {
// This works, so I know I'm getting the right component.
console.log(
myApp.views.pList.getComponent('pResultsList').getComponent('resultsList'));

// This works, so I know the component is responding to available commands.
myApp.views.pList.getComponent('pResultsList').getComponent('resultsList').hide();

// However, this does not work...
// myApp.views.pList.getComponent('pResultsList').getComponent('resultsList').disable();

// Neither does this...
// myApp.views.pList.getComponent('pResultsList').getComponent('resultsList').setDisabled(true);

}
}
}
}],
initComponent: function() {
coupoza.stores.products.load();

this.items = [
id: 'resultsList',
xtype: 'list',
// .
// .
// .
];
coupoza.views.ProductResultsList.superclass.initComponent.apply(this, arguments);
}
});
//Needed to register this view as an xtype
Ext.reg('pResultsList', myApp.views.PResultsList);

Limbo
15 Sep 2011, 3:41 PM
I too am having this problem in 1.1.

How can I disable the list?

I've tried .setDisabled(true) and .disable(), but it doesn't work :(

anselmtmcclain
23 Sep 2011, 2:15 PM
Running into the same issue here as well. Any updates would be welcome as the bug is marked as fixed.

Thanks - ATM

mbalsam
27 Feb 2012, 5:17 AM
I can verify that this is still an issue in 1.1.x. Anyone bother to give an update?