Hello Allan & fellow forum members,
I've encountered a strange problem using fnDeleteRow and decided to seek here some advice...
When I've tried using fnDeleteRow( [ TR element] ) to delete a certain row, the NEXT row was being deleted to the one I was actually passing as a parameter.
Then, I've decided to try and use an index parameter instead just to see what happens....
For example: fnDeleteRow(0).
What I found was that the second row (which is supposed to be index 1) was being deleted instead of the first row (index 0).
In general, fnDeleteRow was working with an +1 offset - deleting the next row which I didn't want to delete instead of the previous one.
It's like the rows index starts from the second row instead from the first row.
I have no idea what's causing this strange behavior. Bug? Usage problem?
Any ideas ?
I've encountered a strange problem using fnDeleteRow and decided to seek here some advice...
When I've tried using fnDeleteRow( [ TR element] ) to delete a certain row, the NEXT row was being deleted to the one I was actually passing as a parameter.
Then, I've decided to try and use an index parameter instead just to see what happens....
For example: fnDeleteRow(0).
What I found was that the second row (which is supposed to be index 1) was being deleted instead of the first row (index 0).
In general, fnDeleteRow was working with an +1 offset - deleting the next row which I didn't want to delete instead of the previous one.
It's like the rows index starts from the second row instead from the first row.
I have no idea what's causing this strange behavior. Bug? Usage problem?
Any ideas ?