Docs regarding suspendRender and resumeRendere are missing information that in order to resume rendering, resume must be called AT LEAST as many times as suspendRender was called.
Please add info to the docs (unless it is a bug)
suspendRender/resumeRender docs not mentioning statcking
We have this information here https://handsontable.com/docs/batch-operations/#suspend-and-resume-methods
That is a simple example with only one use of those two methods. But it is said that one has to remember to call resumeRender() after they called suspendRender().
Also, we use those methods internally so if one does not turn of the suspension they might get some serious issues with the table.
But it does not state that number of calls to suspend/resume must match which is not obvious. For example I was expecting that if I call suspend X time then 1 resume will be enough, which is not true.
Look at it this way
To suspend the rendering process, you can call the
suspendExecution
I did it - multiple times
After suspending, you must remember to resume the process with the
resumeExecutionmethod.
and I did, once after everything is done and it didnt work.
What I did is a very intuitive way of interpreting suspend/resume as enable/disable things. If you disable something multiple times - it is always in the same disabled state. After that if you enable it - well it is enabled.
This is something I have bumped into and had to figure it out myself a first time HOT API user. To me it is just not stated there and I had to figure it out myself.
You are right. We should avoid any ambiguous descriptions. I have added your proposition to the list of issues for DOCS at https://github.com/handsontable/handsontable/issues/9287
Thank you for sharing and reporting, @sebastian.choina