EnSight Binary uses 64bit longs so explicitly use those instead of long.

Using just long as the type will fail on window machine where long
size is 4 unlike Posix machines where it is 8. So we use the vtkTypeInt64
type which is always 8 bytes long.

Change-Id: Ib61d5e1860c411e44153904b497c525f392d2f32
Merge topic 'ensight_binary_time_caching' into master

278b3c66 EnSight Binary uses 64bit longs so explicitly use those instead of long.
Catalyst-web: Improve composite search experience

Change-Id: I49e266fbf1f7e26d28f8a9e1bb1e3bc6a1446621
Merge topic 'catalyst-web-composite' into master

b19eaa4f Catalyst-web: Improve composite search experience
do not assume 1st column holds row names

As of this commit, we no longer assume that the 1st column of
the input table specifies the names of the table's rows.  Instead,
we search by default for a column named "name".  The user can
change the name of this array by calling vtkHeatmapItem::
SetNameColumn(vtkStdString).  We fallback to using the 1st column
only if no such array can be found by name.

Change-Id: I2494ff21f3efa4a379dce82e159715dc023d8995
Merge topic 'heatmap_row_names' into master

729fe63f do not assume 1st column holds row names
Add image width column

Change-Id: If6296d6b05dd3773f93a18a62db8f7a3e32b247c
Merge topic 'catalyst-web-composite' into master

cfcebd10 Add image width column