In my grid, I am updating it to use the Virtualization of Remote Data (and removing the discrete paging via next/previous buttons). In the code, I am changing from scrollable: false to scrollable: { virtual: true }.
The side effect of this is that my columns, which were sized according to the content (when scrollable was false) are now all the same width. Note that I do not have any widths set on any of the columns.
What I would like is to be able to transition to virtual paging (virtual scolling or whatever it's called) and retain the auto width of the columns.
Thinking about it, it does make some sense. You don't know the width of the data that has not yet been populated into the grid like you do with discrete pages (via next/previous buttons). But, Kendo must have a method to autosize the columns to the content that I can, at the least, call myself to autosize in the dataBound event when the first page is done fetching data?
Thanks,
--Ed
The side effect of this is that my columns, which were sized according to the content (when scrollable was false) are now all the same width. Note that I do not have any widths set on any of the columns.
What I would like is to be able to transition to virtual paging (virtual scolling or whatever it's called) and retain the auto width of the columns.
Thinking about it, it does make some sense. You don't know the width of the data that has not yet been populated into the grid like you do with discrete pages (via next/previous buttons). But, Kendo must have a method to autosize the columns to the content that I can, at the least, call myself to autosize in the dataBound event when the first page is done fetching data?
Thanks,
--Ed