Re: Thread problems with javax.swing.Timer?

From:

Daniel Pitts <newsgroup.spamfilter@virtualinfinity.net>

Newsgroups:

comp.lang.java.gui

Date:

Fri, 08 May 2009 08:15:38 -0700

Message-ID:

<v0YMl.33803$5N7.18583@newsfe09.iad>

Sabine Dinis Blochberger wrote:

Giampiero Mughini wrote:

Sabine Dinis Blochberger ha scritto:

A compilable example would help [1].
My guess is that whatever your timer does, should go into an invokeLater
block. See EventQueue [2]. Example:
    SwingUtilities.invokeLater(new Runnable() {
        @Override
        public void run() {
     // your code
        }
    });

protected void startCounter() {

               if (timer!=null)
                       timer.stop();

               timer = new Timer(1000, new ActionListener() {
                       public void actionPerformed(ActionEvent arg0) {
                                       updateDisplay();
                       }
               });
               timer.setInitialDelay(0);
               timer.start();

       }

Should I put the call to the method updateDisplay() into an invokeLater
block?

If it does anyhting with the Swing GUI, yes. You can also put the wrap
inside the method.

Except that Swing timer dispatches on the EDT, the code doesn't need to
invokeLater.

<http://mindprod.com/jgloss/swingthreads.html>
<http://java.sun.com/docs/books/tutorial/uiswing/concurrency/>

I'm guess that the original method is still running? You're blocking the
EDT, If you have long-running work that needs to happen, then you need
to move it off of the Event Dispatch Thread.

--
Daniel Pitts' Tech Blog: <http://virtualinfinity.net/wordpress/>