Remembering Window State

Question

Various threads have addressed parts of this topic, but I haven't seen a complete workable solution so far. Here's the problem:
When my application starts, it's supposed to restore its main window (a JFrame) to the state it had when it was last closed (unless it was minimized). If it was maximized, it should maximize automatically, otherwise it should open with the same location & dimensions it last had. As the application runs, I monitor changes in size, location & maximized state, then save them to a properties file when it exits.
Mostly, this is working OK, but I'm having a problem the ComponentListener. When the user maximizes the window, the componentMoved method is called, but at that point the Frame state doesn't indicate the window is maximized. So I save the window coordinates, but they turn out to the wrong coordinates, because the window is maximized. Here's my componentMoved method:
* Saves new position when frame moves.
* @param event The event being handled.
public void componentMoved(ComponentEvent event)
   Object source = event.getSource();
   if (source instanceof UprrFrame)
      UprrFrame frame = (UprrFrame)source;
      if (frame.isMaximized() == false)
         frame.saveBounds();
}The frame.IsMaximized method looks like this:
* Determines whether the frame is currently maximized.
* @return <b><code>True</code></b> if maximized.
public boolean isMaximized()
   int state = getExtendedState();
   boolean maximized = (state & Frame.MAXIMIZED_BOTH) == Frame.MAXIMIZED_BOTH;
   return maximized;
}I'm, not sure if I'm doing something wrong, or whether I've stumbled across an AWT/Swing bug. Any insights would be greatly appreciated!
P.S. I'm running JDK 1.4 under Windows XP.

Answer 1

If your solution works for you, then thats all good. However, i'll add this for completion...
Actually, the invokeLater in componentMoved does not always work in this case... it might seem to work all the time, but in reality, it's just luck that it's working. If you test it in enough environments, or with slower machines, you'll see what I mean.
Basically, you are trying to time it so that the test for frame maximization occurs after the window state change event. However, the window state change events are caused by asynchronous native window events.. and if the machine is slow enough (or perhaps fast enough), the invoke later is executed too sonn, and it says the frame is not maximized when it is.
You need to save the window location in componentResized, and rollback the save transaction when you hear a window state changed event from NORMAL -> BOTH_MAXIMIZED.