OMEdit badly truncates numerical values

[massimo ceraolo]

I have a machine that has as Lstray the value

0.0006480774127832951

If I look at it in the Variable browser while limiting the available horizontal space, the number is truncated in its internal part. For instance it might appear as:

0.000...32951 or 0.0006...832951

which is illogic.

Numerical values should be truncated in their right (not the internal) part.

[massimo ceraolo]

... unless they are in exponential form, in which case dropping the internal part when the available space is insufficient makes sense.

[Francesco Casella]

Rescheduled to 1.14.0 after 1.13.0 releasee

[Adeel Asghar]

Done in bef7e4f/OMEdit.

[massimo ceraolo]

Looking at your code it seems that you did not consider comment3

[Adeel Asghar]

Yeah that's true. I didn't even noticed the comment.

Well its hard to know if the number is a regular decimal value or is in exponential form. I could use some regular expressions to check for it but is it really needed?

[Francesco Casella]

I guess something like

if strstr(number, "e") || strstr(number,"E")
  {
  // truncate in the middle, keep last 4 characters
  }
else
  {
  // truncate at the end
  }

would do :)

[massimo ceraolo]

Well its hard to know if the number is a regular decimal value or is in exponential form. I could use some regular expressions to check for it but is it really needed?

It is not very much needed, but would be a nice feature to have. In other words would enhance the quality of OMEdit.

If you want to implement smart truncation, i.e. correct number display whether their are in exponential form or not, in addition to the proposal by Francesco, a simple option is to use

QString::setNum(double n, char format = 'g', int precision = 6)

with 'g' format and variable precision.

This should be safer: Francesco's solution takes for granted that the number of characters for exponent in number strings is always the same, which might not be the case for all OS's, depending on how you create those strings.

[Adeel Asghar]

I don't prefer to modify the values received from omc. I prefer Francesco's solution but of course without assuming that the characters in the number are always same.

ce509a3/OMEdit fixes this.

[massimo ceraolo]

Replying to adeas31:

I don't prefer to modify the values received from omc. I prefer Francesco's solution but of course without assuming that the characters in the number are always same.

ce509a3/OMEdit fixes this.

Good. I did not know that you receive strings (not numbers)