Hey,
yes, that is understandable. In my real-world example I’d update the underlying data after some action (add, update, …) is done using the everpresentrow.
But this topic is not about the data-update as reaction to everpresentrow events. The topic is that the everpresentrow itself breaks as soon as some KO observable array operation is done (adding / removing via the upper buttons).
You can see that adding a new row via the everpresentrow, after that, results in an empty grid row. I debugged locally and found out that the HTML input element in the everpresentrow is not correctly adressed anymore (its .val() call returns ‘undefined’).
So, this is something I’d like to know, is there a workaround (resetting the everpresentrow somehow when some changes occur in the KO observable array)?
Thanks,
Tim