property 1 is incorrectly displayed

[nathanfranklin]

Version 6.5, commit b29c73a

Input file:

10
#XZYfile
X0 1.9265350878690097e+00 1.2235141067428751e+01 -9.0000000000000000e+00 1.0 1.0
X0 1.9907529241313100e+01 1.2235141067428751e+01 0.0000000000000000e+00 2.0  2.0
X0 2.5044956142297124e+01 7.7859988610910245e+00 0.0000000000000000e+00 2.0 2.0
X0 2.2476242691805112e+01 1.4459712170597616e+01 0.0000000000000000e+00 2.0 2.0
X0 1.0274853801968051e+01 1.3347426619013184e+01 0.0000000000000000e+00 2.0 2.0
X0 1.2843567252460064e+01 1.7796568825350910e+01 0.0000000000000000e+00 2.0 2.0
X0 1.6696637428198084e+01 1.5571997722182049e+01 0.0000000000000000e+00 2.0 2.0
X0 2.4402777779674121e+01 2.0021139928519776e+01 0.0000000000000000e+00 2.0 2.0
X0 1.2843567252460064e+01 6.6737133095065921e+00 0.0000000000000000e+00 2.0 2.0
X0 7.7061403514760389e+00 1.1122855515844320e+01 3.0000000000000000e+01 5.0 5.0

Property 2 (which has the exact same values) is properly displayed, but property 1 is displayed incorrectly.

[nathanfranklin]

@simphony/iit @joanadler @simphony/fraunhofer-iwm

[ahashibon]

from the figure it looks like the color scale is zero, so searching for the color scale range leads to glCanvasFrame.cpp which shows that indeed, the minimum value for the p1 (property 1) is not calculated for some reason (all other properties are correctly calculated).
so adding this:
if ((_ad).particles[i].prop1 < p1min)
p1min = (_ad).particles[i].prop1;
solves this problem.
I will upload a branch for testing.

[nathanfranklin]

closed by #36