Right now I'm getting tracepoints that read:"d[-1, 1]=(-0.25000000000000006, -0.24999999999999997)" when what I want to see is (-0.25, -0.25). This makes things harder to see, muddies up the output and forces me to scan through a bunch of 0's or 9's to see where my last actually significant digit was. Even, if it weren't for the problem of "near" values, I don't generally want to see sixteen digits of Sin(20) either. It just takes up values screen space and messes with what little control I have over the UI arrangement of values in the tracepoint output already.
Customer support service by UserEcho