Re: Precision problem for ValueBoxBaseLong ?

2011-06-22 Thread Eric Andresen
Kishan, I was able to work around the bug by extending LongParser and LongRenderer with the following: @Override public Long parse(CharSequence object) throws ParseException { if (.equals(object.toString())) { return null; } try { return

Re: Precision problem for ValueBoxBaseLong ?

2011-02-17 Thread Eric Andresen
Here is the simplest code to reproduce the problem: Long number = 6920835985627925859L ; logger.severe(Original + number); logger.severe(From renderer: + LongRenderer.instance().render(number)); logger.severe(From parser: +

Precision problem for ValueBoxBaseLong ?

2011-02-16 Thread Eric Andresen
I have an editor that uses a ValueBoxBaseLong to store a very large number. The box is read-only, but it my number gets changed between setValue() and getValue(). Basically, when I set value 6920835985627925836 and then immediately get the value, it returns 6920835985627925504 . The value