Closing a JFrame

[Guy Shahar]

Probably a very obvious answer to this one, but I can't find it.

I want to close a JFrame during the running of a program without killing the object that created it. I have looked for a frame.close() or frame.exit() method, but they don't seem to exist.

Is there an easy way of doing this?

[Nick Meverden]

if you want to hide the JFrame use setVisible(false) if you want to remove the JFrame and release its resources use dispose()

[Guy Shahar]

Thanks Nick

This works and the frame disappears. Does it really free all the resources of the frame?

I ask because when I clicked for the frame to be recreated, it appeared in the same place on the screen as it had been when I clicked for it to be closed. (or maybe this was within the memory of the object??)

Thanks

Guy

[Nick Meverden]

Releases all of the native screen resources used by this Window, its subcomponents, and all of its owned children. That is, the resources for these Components will be destroyed, any memory they consume will be returned to the OS, and they will be marked as undisplayable.

The Window and its subcomponents can be made displayable again by rebuilding the native resources with a subsequent call to pack or show. The states of the recreated Window and its subcomponents will be identical to the states of these objects at the point where the Window was disposed (not accounting for additional modifications between those actions).

[Gregg Bolinger]

That's good info Nick. Unfortunately, you didn't state where you got that information. So I'll do it for you.

Java API - Window class

Guy, the API is a wonderful and invaluable tool for us Java developers. Be sure and bookmark it. It can save you a ton of time once you learn how to use it.

[Guy Shahar]

Thanks Gregg

Yes, I know about the API - my only problem is that when there is something I want to do, it is not always obvious where in the API I need to look to find it....

[Gregg Bolinger]

Originally posted by Guy Shahar:
Thanks Gregg

Yes, I know about the API - my only problem is that when there is something I want to do, it is not always obvious where in the API I need to look to find it....

I totally agree. Starting with the method you don't understand in the class that contains said method is usually a good start. The API takes a bit of getting used to. I often find myself in moments because I forgot about the API.