Hi, I just wanted to follow up on this one. We just installed the recently released version 19.2.49 and this issue is not yet resolved. Do you have an updated estimate on when it might be?
onClick() {
this.pivotObj.gridSettings.columnWidth += 20; // Here you can modify column width dynamically for all columns except first.
//this.pivotObj.resizedValue = this.pivotObj.gridSettings.columnWidth; // By using “resizedValue” property you can change first column width dynamically.
this.pivotObj.layoutRefresh();
} |
Hi,
This wasn't exactly the change we were hoping for. Now, the user cannot resize columns in the pivot grid, which can be an issue if the data in the header or the cell is too long to fit in the width. At least before they could resize the columns. Is there any way you can make this behavior optional? I think we preferred it the way it was.
Additionally, we did find some odd behavior when testing this out. While you can't manually resize any column after the first one any more by grabbing the boundary and moving the mouse, we did find that if you double-click the column boundary, the column will resize to fit the contents of the widest cell in the column. At first we thought this might be a workaround to not being able to manually resize the column, but then we found if you double-click another column boundary, all the columns revert to their original width. So at most you can only resize 1 column beyond the first one using this technique (which seems to be unintentional).
Thanks,
Michael
Query |
Comments | |
This wasn't exactly the change we were hoping for. Now, the user cannot resize columns in the pivot grid, which can be an issue if the data in the header or the cell is too long to fit in the width. At least before they could resize the columns. Is there any way you can make this behavior optional? I think we preferred it the way it was. |
In virtual scrolling, horizontal scrolling operations will be performed based on “columnWidth” property in “gridSettings”. If we modify the column width for specific column header, the modified column width will not be considered for scrolling calculation and it leads to performance oriented problems, while considering it when we have many column headers. However, you can modify the column width for columns other than the first column by using “columnWidth” property in “gridSettings”. Kindly refer to the following code example and sample.
Code Example:
| |
Additionally, we did find some odd behavior when testing this out. While you can't manually resize any column after the first one any more by grabbing the boundary and moving the mouse, we did find that if you double-click the column boundary, the column will resize to fit the contents of the widest cell in the column. At first we thought this might be a workaround to not being able to manually resize the column, but then we found if you double-click another column boundary, all the columns revert to their original width. So at most you can only resize 1 column beyond the first one using this technique (which seems to be unintentional). |
This is a known issue, and it will be included in our upcoming Volume 2 SP 1 release which is expected to be rolled out next week. |
In regards to the first issue, our users need the ability to manually resize individual columns, so resizing them by a fixed amount programmatically is not an option. I do understand your concern about performance considerations.
I noticed that even if I set enableVirtualization='false' I still can't resize the columns. Is that intentional as well? We set this to true because there could be a lot of rows or columns in the pivot grid since our users often work with large data sets. If we could get it so the columns were resizable when not using virtualization we could make the virtualization dependent on the # of rows/columns which would be a fair compromise, not allowing users to resize if they are working with a very large dataset.