title: In Java, AWT, repaint-method seems to be ignored in favor of start-method
body: <p>I'm building an applet of a board game, and handling user input roughly looks like this:</p>
  
  <pre><code>public void mousePressed(MouseEvent event) {
      int row = event.getX() / (getSize().width / 8) ;
      int column = event.getY() / (getSize().height / 8) ;
      if(possibleMove(column, row) {
          makeMove(column,row,whosTurn); 
          repaint();
          start();
      }
  }
  </code></pre>
  
  <p>After a human input, the computer chooses a move and calls repaint() and start() like this method does.<br>
  But the screen seems to update only after the computer has made a move, so after start() is called. How can this happen, since repaint() is called before start()? </p>
  
  <p>I have a suspicion this might be because repaint() launches a new thread (does it?), but why would it wait for start()?</p>
  
  <p>I could provide more code if necessary, of course.</p>