🚀 go-pugleaf

"Joi Ellis [TeamB]" wrote:

> Kevin Dwan <kevin@blueberry.com> wrote:
>
> > Thanks, Joi. That did it.
>
> > Do you have a suggestion for clearing the JList, so that if the user changes the
> > selection, the old values get zapped?
>
> > I thought JList1.clearSelection would do it, but it does not.
>
> Isn't this from a JFileChooser?  The user will have already made and unmade
> whatever selections they wish.  It isn't until they press <ok> or whatever
> you named the accept button that the getSelectedFiles() method will return
> anything.
>
> JList1 is your own copy of the data list, it isn't the same list as the
> user is seeing embedded within the JFileChooser.  You can do anything you like
> to JList1 and it won't affect the JFileChooser.
>
> --
> Joi Ellis (TeamB)
> No direct email, please.
> For best results, post on news server newsgroups.borland.com!

Yes, the selections do come from a JFileChooser, and are written to the JList in
another panel. Since this other panel gives the user other decisions, it's to be
expected that sometimes users will page back to the first panel and change their
selections in the chooser. So I need to clear out the selections in the JList, if
there were any, at the head of my Approve button actionevent, and the
JList.clearSelection method isn't doing it. (I also need to do this action of clearing
the JList listing if the user presses my homegrown "Cancel Selections" buton.)

The problem may be that the default list model of a JList is immutable, and I have to
do something like set the JList to DefaultListModel with the setModel method, and then
zap the choices by operating on the instance of the ListModel. I tried doing this
using the ListModel's .clear() and .removeAllElements() methods, but they don't seem
to work as I expected either.

I didn't think it would be this difficult to just erase the list.