Thanks for that article. The best part about that article is John Brinkman's comment on referencing the instance manager object in a calculation event instead of using both the calculation event and the indexChange event.
Consider this, say you want a numbered list of rows that increments the number everytime you add a row. In the calculate event of a cell in the row you would put this.rawValue=this.parent.index+1;
but of course if you delete the first row it doesn't recalculate and your left with a set of rows starting with 2. Well I've always put in the indexChange event of the row NumField.execCalclulate(); to refresh the field when a row was deleted. Well try this two liner in the calculate event of the field alone without any code in the indexChange event of the row:
var i=_RepeatableRow.count; //it's only use is to trick the
//calculate event mitigating the need for indexChange event code
this.rawValue=this.parent.index+1;
Here, I inserted a 'useless' line of code (var i=_RepeatableRow.count) for the sole purpose of tricking the calculate event into thinking it's referencing the instance manager object. When the objects count property changes from the deletion of a row, it fires the event. Cool.
Kyle
