Skip to main content

How can i make an event to a JComboBox which triggers AFTER selection?



I want to make an event which will be triggered after i make the selection to the JComboBox. the problem I'm now facing is that when i added an ActionListener, it was triggered when the user clicked on the box but BEFORE he actually chose the new item, thus the action listener was activated all the time on the previous value which was selected in the box. what i want to do is simply changing the title of an JTextArea according to the selection. I tried doing something like this:







jBox.addActionListener(new ActionListener(){

@Override

public void actionPerformed(ActionEvent e) {

String alt = GetAlgoAreaTitleByChoice();

panel.remove(jArea);

currentBest = setArea("",alt);

currentBest.setBounds(50, 350, 1000, 290);

panel.add(jArea);

}

});







and the method inside:







private String GetArgsAreaTitleByChoice(){

String chi = jBox.getSelectedItem().toString();

if(chi.equals(generalChoice)){

return "Hello";

}

else if(chi.equals(algoChoice)){

return "World";

}

else if(chi.equals(argsChoice)){

return "Hello";

}

return null;

}







I've tried using the SELECTED events now like this:







public void itemStateChanged(ItemEvent e) {

JComboBox cb = (JComboBox)e.getSource();



// Get the affected item

String item = cb.getSelectedItem().toString();



if (e.getStateChange() == ItemEvent.SELECTED) {

panel.remove(jBox);

textArea = setArea("", item);

panel.add(jBox);

}







but it seems to remove the area from the panel without adding it back... why is this happening?


Comments

  1. For listening of events from JComboBox is better implements ItemListener, returns two events SELECTED/DESELECTED

    EDIT

    if you remove/add JComponent(s) on Runtime and in already visible container, then you have to call (as least code lines)

    revalidate();
    repaint();

    ReplyDelete
  2. Here is a simple demonstration with a sample code :

    import javax.swing.*;
    import java.awt.*;
    import java.awt.event.*;

    public class Tester {

    public Tester(){

    JComboBox box = new JComboBox();
    box.addItem("One");
    box.addItem("Two");
    box.addItem("Three");


    box.addItemListener(new ItemListener(){
    public void itemStateChanged(ItemEvent e){

    if(e.getStateChange()==ItemEvent.SELECTED){

    e.getItem(); //Do what ever you want :))

    }
    }
    });

    JFrame frame = new JFrame();
    frame.getContentPane().add(box);
    frame.pack();
    frame.setVisible(true);
    }

    public static void main(String [] args) {
    Tester tester = new Tester();
    }
    }

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex