>>>>>>The copy doesn't work with the unmodified latest version either (I removed that last parameter). I am going to restore to the version we had prior to that and re-try.
>>>>>>
>>>>>>I undid my changes (reverted to old version of ng-grid), but yet grid refuses to show data :(
>>>>>
>>>>>Trying things at random means you are just thrashing around. If something doesn't work then debug 'till you find out why - then look for the solution.
>>>>
>>>>Going back to the version supposed to be working is not trying things at random IMO.
>>>
>>>'supposed to be working' is the key phrase - sometimes Naomi thinks it is working, sometimes not. The problem is that she doesn't know why it is/isn't working - and without that knowledge it's impossible to know whether a modification will, or will not, truly fix the issue.......
>>>
>>
>>At least she has now a data point: it was not working when she thought it was working. Further backtracking might find a working version or at least cut down the amount of changes to check. I still think the latest approach is better then the previous attempts, on the assumption of massive changes to check or oodles of code to debug.
>
>AFAIK there was no previous working version and the relevant code that requires debugging is relatively small. At the end of the day if you want to fix a problem (and *know* that it is fixed) you have to identify the cause.
>

Full ACK on the need to identify the cause. But stripping own code away on a foreign control is a sound idea, as it eliminates (in this case as well) code not responsible for the misbehaviour. Going in and adding code before trying out new other controls and having a valid map of what is working and what not is not something I would do - so your key phrase is correct.