{ headerText: "Product ID", key: "ID", dataType: "number", width: '130px' },
{ headerText: "Product Number", key: "ProductNumber", dataType: "string", width: '60px' },
{ headerText: "Product Number2", key: "ProductNumber2", dataType: "string", width: '60px' },
{ headerText: "Product Number3", key: "ProductNumber3", dataType: "string", width: '60px' },
{ headerText: "Product Number4", key: "ProductNumber4", dataType: "string", width: '60px' },
{ headerText: "Price", key: "Price", dataType: "number", width: '60px' },
],
{
name: 'Sorting',
type: "local"
},
name: 'Resizing',
deferredResizing: true
Hi,
Actually I just spotted that you are using rowVirtualization in order to render a large volume of records.
When any form of virtualization is used on the grid, you will not be able to change options such as width or height at runtime. The reason is that the grid's DOM is much more complex when there's virtualization so changing virtualization-dependent options such as the grid's width or height would cause a potentially slow and resource-intense recalculations and re-rendering.(So it's not really a matter of whether the grid is bound to a TABLE or a DIV)
My suggestion would be to destroy and re-initialize the grid with the new width when you are using virtualization.
PS: Thank you very much for these sort of solid code samples in your posts - they're really helping us reproduce and process such questions :)Best Regards,Borislav