I’d suggest to use showConfirmDialog instead int result = JOptionPane.showConfirmDialog(myParent, “Narrative”, “Title”, JOptionPane.INFORMATION_MESSAGE); and there you can test for various returns value from JDialog/JOptionPane if (result == JOptionPane.OK_OPTION, JOptionPane.CANCEL_OPTION, JOptionPane.CLOSED_OPTION, etc..
If you don’t need much in the way of custom behavior, JOptionPane is a good time saver. It takes care of the placement and localization of OK / Cancel options, and is a quick-and-dirty way to show a custom dialog without needing to define your own classes. Most of the time the “message” parameter in … Read more
Here an updated version of your code which works import java.awt.EventQueue; import java.awt.event.ActionEvent; import java.awt.event.ActionListener; import javax.swing.JButton; import javax.swing.JDialog; import javax.swing.JFrame; import javax.swing.JLabel; import javax.swing.JProgressBar; import javax.swing.SwingWorker; public class SwingTesting { public static void main(String[] args) { EventQueue.invokeLater( new Runnable() { @Override public void run() { JFrame frame = new JFrame(); JButton button = new … Read more
As discussed in Sizing a Scroll Pane, some components can provide useful information about setting the viewport’s preferred size. The setVisibleRowCount() method of JList is particularly convenient, but even getViewport().setPreferredSize(…) may suffice. Naturally, an sscce would help. Addendum: As a concrete example, the dialog below is initially sized to have N-2 rows. As more are … Read more
When dynamically adding/removing components from a container, it’s necessary to invoke revalidate()/validate() and repaint() afterward. The former will force the container to layout its components again and the latter will remove any visual “artifacts”.
Invoking dispose() allows the host platform to reclaim memory consumed by the heavyweight peer, but it can’t do so until after the WINDOW_CLOSING event is processed on the EventQueue. Even then, gc() is a suggestion. Addendum: Another way to see the nightmare is via a profiler. Running the example below with jvisualvm, one can see … Read more