I've tried the "destroy and re-initialize" method and that doesn't work either. Plus, it's messy.
Justin, I think this is kind of a bug.
I have no problem not being able to use live binding with the datagrid, but I don't like that it breaks my app.
Shouldn't there be a way to be able to use .attr() in an EJS file and have it not turn on live binding?
My model has a lot of convenient prototype functions that use .attr() that are used throughout my app and used in the EJS file that generates the HTML for the table. I don't want to have to have duplicate functions so I can have ones that don't use .attr()
Are you saying that is what I have to do?
At a minimum this needs to be documented with the live binding as a "you can't do this" item.
If you give me some directions, I can try and help out developing a fix. I am rather motivated.