import java.awt.*;
import javax.swing.*;
import javax.swing.event.*;

public class UsingSpinner implements ChangeListener
{
public UsingSpinner()
   {
   JFrame MainFrame = new JFrame();
   SpinnerModel Model = new SpinnerNumberModel(10, 0, 100, 0.1);
   Model.addChangeListener(this);
   JSpinner MySpinner = new JSpinner(Model);
   MainFrame.getContentPane().add(MySpinner);
   MainFrame.setSize(300, 100);
   MainFrame.setVisible(true);
   }

public void stateChanged(ChangeEvent ce)
   {
   Double value = new Double(0);
   value = (Double)((SpinnerNumberModel)ce.getSource()).getValue();
   System.out.println(value.doubleValue());
   }

public static void main(String arg[])
   {
   UsingSpinner MySpinner = new UsingSpinner();
   }
}

On Aug 15, 2:43 am, Roedy Green <see_webs...@mindprod.com.invalid>
wrote:

Looking at his SSCCE, I've noticed the same behavior, but here's
exactly what I notice...

"Spinning" the value up or down will sometimes cause a non-exact
floating point number (11.29999999999999).  The next click after that
will cause two values, first the rounded version, THEN the new current
version.

Very odd indeed.

This can be avoided. Make each event handler a separate instance of some
class implementing the appropriate interface. Put an ivar like this in:

private boolean inHandler = false;

and in the handler method,

if (inHandler) return;
inHandler = true;
try {
.
.
.
} finally {
        inHandler = false;
}