>>>>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.

And yes, sometimes such posts make me think of Wonderland, but OTOH I was once asked to take over a large package and to start by cracking a few tough nuts on the error list. You can guess how I felt when I was able to prove that the versions in source safe did in no way reflect the versions rolled out in the last 29 months. Before that I was trying to repro some errors and/or the doc'ed behaviour from versions created from the labeled source safe: made me doubt my sanity a few days.

Refoxing the rolled out versions as well as versions created from SS labels and piping the differences into a file to print out and make a nice present of to the manager made me smile a lot...