You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using a provider model, similar to the remote model, with very large datasets. We recently ran into an issue where the data set is larger than the 32-bit int safe max value of 2,147,483,647. When calling getCellFromEvent via a context menu click we are getting a negative number returned as the row.
Within getRowFromNode it is currently returning a bitwise or operation to ensure that the value is an integer. When returning a number larger than the 32-bit safe int max it starts rolling into negative numbers.
I've tested locally by changing the return value in getRowFromNode to return return +row without any noticeable bugs and returning the correct row number.
If you have any alternative ways to get the row from the context menu click, without going through the getCellFromEvent, we are open to hearing about it as well.
Thanks
The text was updated successfully, but these errors were encountered:
We are using a provider model, similar to the remote model, with very large datasets. We recently ran into an issue where the data set is larger than the 32-bit int safe max value of 2,147,483,647. When calling
getCellFromEvent
via a context menu click we are getting a negative number returned as the row.Within getRowFromNode it is currently returning a bitwise or operation to ensure that the value is an integer. When returning a number larger than the 32-bit safe int max it starts rolling into negative numbers.
I've tested locally by changing the return value in
getRowFromNode
to returnreturn +row
without any noticeable bugs and returning the correct row number.If you have any alternative ways to get the row from the context menu click, without going through the
getCellFromEvent
, we are open to hearing about it as well.Thanks
The text was updated successfully, but these errors were encountered: