I’m having a problem adding a split to one of my grid objects and was wondering if you could help.
I have attached the file that can reproduce the problem for reference. Essentially, I have a grid that is working exactly as expected, but when I try to add a split on the first column (or any column for that matter) the page hangs for a few minutes and then returns a malformed grid. It occasionally throws an “Uncaught RangeError: Maximum call stack size exceeded” in the console as it seems to be caught in an infinite loop calling setSizes.
Interestingly, if I comment out the line
grid.enableAutoWidth(true, 500, 400);
then the split is correctly added to the grid, however I do need to keep this line for formatting. Are these two functions not compatible with each other?
I have also attached screenshots for reference.
Any help you could offer would be much appreciated.
Unfortunately the split mode is incompatible with teh autoWidth mode.
Could you clarify what behavior do you expect from from such a combination.
In case of using the autoWidth mode the grid container will fit it’s width to the columns width so that there is no horizontal scrollbar in your grid.
In case of using the split mode grid is divided in two parts so that the user may see the left side of the grid dragging the horizontal scroll bar to the right.
If you have no horizontal scrollbar there is no need in the split.
I’m hoping to be able to set the width of the grid so that it fills the width of it’s parent container whilst maintaining the frozen columns. Would you be able to give me some pointers? Thanks.
I’ve set the container to have a width of 100% which is fine, however when I call setSizes() on the grid itself, the width is set to a value of 0. I have confirmed that the grid does have data at this point, and if I manually increase the width of the grid in the browser developer tools it looks fine. Is there something I should be doing before calling setSizes()?
Please, provide with the code snippet of your grid initialization.
Or share with a demo link/provide with a simple complete demo, where the problem can be reproduced.
Unfortunately the problem cannot be reproduced with the provided code.
If the issue still occurs for you please, provide with a complete demo or share with a demo link, where the problem can be reconstructed.
Get a guaranteed answer from DHTMLX technical support team
under the most suitable support plan