🚀 go-pugleaf

thanks, Rich, you're a helpful guy.  (I'm still getting the hang of swing,
if you'll pardon the expression).

Richard Wilkman wrote:

> Alex:
>
> That's exactly what it's supposed to do.  You get one for the item
> that is getting de-selected (it's state changed) and one for the item
> getting selected (it's state changed).  You need to do your own
> filtering in your events so that your code executes only when you want
> it to.  Something like:
>
> void choiceChanged(ItemEvent e){
>
>  if(e.getStateChange() == ItemEvent.SELECTED){
>    // do whatever
>  }
>
> }
>
> -Rich
>
> Alex Humphreys wrote:
> >
> > I have a JdbComboBox with an ItemStateChanged event.  Problem is that
> > when I choose an option in the comboBox, it fires the ItemStateChanged
> > event TWICE.  It runs all the way through it once, and then goes into
> > some jdbComboBox code and then the event gets fired again.  What's
> > happening?  This didn't happen before I was using Swing.
> >
> > Any ideas?  I can provide code if that would be helpful....
> >
> > Thanks.
> >
> > Alex
>
> --
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Rich Wilkman
> Senior Quality Assurance Engineer
> Borland JBuilder Team
>
> If you see something that looks like an opinion up there,
> it's mine and mine alone.
>
> Mail sent to me from the newsgroups won't bounce but will
> be ignored.  If I have time, I'll respond, but you  have
> a better chance if you confine your posts to the newsgroups
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=