Fixed calculation error

Old calculation for MAX/MIN used the precise values for the sides of the triangle, while the display values were rounded, leading to occasional arithmetic errors (and a host of issues on the issues tracker).  

New calculation model uses an additional array to store result of applying parseFloat to each element in KNOWN_DISPLAY and using those values for the calculation of MAX/MIN.  Old bug seems to be fixed.