Updated to use pagingOptions.totalServerItems

[Siyfion]

No description provided.

[sonnyhu]

If using this fix, $scope.$parent.$watch(options.totalServerItems, function (newTotal, oldTotal) won't work. It watches gridOptions.totalServerItems. My solution is that keep the ng-grid source code, and add this code to the controller.

$scope.tempTotal = 0; // tempTotal will be set in an async call.
$scope.totalServerItems = 0; // This will be set in $watch when gridOptions.totalServerItems has changed.
$scope.gridOptions = {
    // If gridOptions.totalServerItems maps to a string, $watch will update its value.
    totalServerItems: 'tempTotal'; 
}

[Siyfion]

@sonnyhu I don't think you've understood my reasoning for this change.

Currently there is a bug with the way $scope.gridOptions.totalServerItems = data.count works, causing the value displayed on the grid to be null. This change is a proposed solution, if the documentation's method of setting the totalServerItems variable is correct. If it isn't correct, then this change is ignored and a bug-fix is needed.

Either way, if you wish to discuss this, please discuss on the actual issue in question (#504).

[jonricaurte]

As said in the other one, "we switched out the place where totalServerItems is set because people
wanted to update it manually while watching the pagingOptions configuration
variable for changes (so they know when to retrieve more data from the
server)." from #332. I'll update the documentation and use the latest version of 2.0.7