Can I disable a button in JOptionPane

import java.awt.*;

import javax.swing.*;

public class DisableButton {

public static void main(String[] args) {

JOptionPane pane = new JOptionPane("Enter some text:");

pane.setInitialSelectionValue("This is the default text");

pane.setMessageType(JOptionPane.PLAIN_MESSAGE);

pane.setOptions(new String[] {"OK", "Cancel"});

pane.setWantsInput(true);

JDialog dialog = pane.createDialog(null, "Disable button test");

findAndSetButton(0, dialog);

dialog.setVisible(true);

System.exit(0);

}

static public void findAndSetButton(int level, Container cont) {

level++;

for (int i=0; i<cont.getComponentCount(); i++) {

Component cc= cont.getComponent(i);

if (cc instanceof JButton){//JButton is instance of Container; so chk 1st.

JButton b= (JButton)cc;

//if (b.getText().equals("OK")) b.setEnabled(false);

if (b.getText().equals("Cancel")) b.setEnabled(false);

}

else if (cc instanceof Container) {

findAndSetButton(level, (Container)cc);

}

}

level--;

}

}

>

Joerg22a at 2007-7-9 6:04:11 >

Which will spectacularly fail on an application running under non-English locale. As a rule of thumb, any time you find yourself iterating over components of some container that doesn't expose its internal structure via an API, there's a good reason behind it and you should rethink your code.

kirillga at 2007-7-9 6:04:11 >

I can only reiterate what i said already - if you find yourself in the need to change the behavior of a predefined dialog (option pane), then that predefined dialog is not for you. The internal implementation which is not exposed via an API is subject to change at any time and you can end up having major maintenance issues.

kirillga at 2007-7-9 6:04:11 >