Store row data for future use in views table preprocess functions

This is needed to solve a problem I encountered while trying to access the data that corresponds to each table row in a preprocess function. Matching the row key with the $view->result key proved to be unreliable. In the case where the view table uses a grouping field, groups are split into their own tables, and $vars['rows'] only contains the data for that specific group, while $view->result always contains the data for all groups.

In my specific case, I was trying to use row data to add classes to my table rows, but couldn't find a way to find the specific data for each row—the data in $view->result[$key] did not always match $vars['rows'][$key], which meant that I couldn't accurately add classes to $vars['row_classes'][$key].

If, for example, my view looks like this:

Group 1
----------
|Result0|
----------
|Result1|
----------
Group 2
----------
|Result2|
----------
|Result3|
----------

Each group is rendered as its own table. When processing the first group, $vars['rows'][0] will correspond to that data found in $view->result[0], but when processing the second group, $vars['rows'][0] will correspond to $view->result[2]. Hope that makes sense.

I thought that storing the original $vars['rows'] array would be a simple way to solve this, but maybe there is a better way?

Are the results in $view->result always in sorted in the order they are presented, even when using a grouping field? My tests show this to be the case, but I don't know if it's necessarily always true. If it is the case, I could count the rows using a static variable, and then reference the results in $view->result using that variable as the key.

@Oleksa It is enough to use the preprocess function in your template.php file. As in the example you posted, you can loop through $view->result and add classes to the $variables['row_classes'][$num] array, with $num being the number of the row. Be aware however that this will not work correctly if you use a grouping field, which is the issue that I was trying to solve in this thread.

I was able to work around the problem by using a global variable to count the number of rows, and use that count to match up the data in $view->result to each row. Here is some sample code:

<?php
/**
 * Preprocess views-view.tpl.php.
 */
function mytheme_preprocess_views_view(&$vars) {
  // Reset the result count
  global $result_count;
  $result_count = 0;
}

/**
 * Display a view as a table style.
 */
function mytheme_preprocess_views_view_table(&$vars) {
  global $result_count;
  if (!is_int($result_count)) {
    $result_count = 0;
  }
  $view = $vars['view'];
  $result = $view->result;
  foreach ($vars['rows'] as $index => $data) {
    // Add classes
    $classes = is_array($vars['row_classes'][$index]) ? $vars['row_classes'][$index] : array();
    // Node language class
    if (isset($result[$result_count]->node_language) && !empty($result[$result_count]->node_language)) { $classes[] = 'node-lang-'. check_plain($result[$result_count]->node_language); }
    // Node status class
    switch ($result[$result_count]->node_status) {
      case "1":
        $classes[] = 'node-published';
        break;
      case "0":
        $classes[] = 'node-unpublished';
        break;
    }
    $vars['row_classes'][$index] = $classes;
    $result_count++;
  }
}
?>