[ xframe-Bugs-1177810 ] setSelectionModel just sets frozenTable's
"SourceForge.net" <[email protected]> Wed, 06 Apr 2005 11:51:08 -0700
| Newsgroups | gmane.text.xml.xframe.xsddoc |
|---|---|
| Message-ID | <[email protected]> |
Bugs item #1177810, was opened at 2005-04-06 16:30
Message generated for change (Comment added) made by kriede
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1177810&group_id=48863
Category: JXTable
Group: swing
Status: Open
Resolution: None
Priority: 5
Submitted By: Iñaqui Medina (inaquimj)
Assigned to: Nobody/Anonymous (nobody)
Summary: setSelectionModel just sets frozenTable's
Initial Comment:
Hi, it's me again (the "nobody" about the setModel
problem). Now I've found a new one:
setSelectionMode(int) works but setSelectionModel
(ListSelectionModel) doesn't (splits the selections again)
the function should be:
public void setSelectionModel(final ListSelectionModel
newModel) {
lockedTable.setSelectionModel(newModel);
scrollTable.setSelectionMode(newModel);
}
----------------------------------------------------------------------
>Comment By: Kurt Riede (kriede)
Date: 2005-04-06 20:51
Message:
Logged In: YES
user_id=484961
Hi Inaqui,
first of all, I want to remind you that the status of the JXTable
is still alpha and we know why: So far we used it only in one
small project and didn't make any exhaustive tests. On the
other hand we think the general design has a good potential
and that's why we released it as Open Source.
In this relation we are very thankfull for any and especially
your tests since the quality improves from day to day.
If you intend to use the JXTable in a productive system, we
would encourage you to do it, but please always keep in mind
the potential risk of an alpha release. Since we (and hopefully
may others) are interesting in a stable release, we will
continue to support you as good as possible. Unfortunately
this will be done in our spare time, so please allow as some
time for fixes.
So now finally about report:
You again found one of the methods where actions are only
taken on one of the tables. Just a single line was missing to
fix it. Changes are checked in into CVS.
I tried to search for other similar problems, but so far I didn't
see any. Anyway I'm quite sure you will find another one.
At last, may I ask you, if (and in the case when) you will use
the JXTable in production? (As soon as we have a reasonable
productive usage, we will upgrade the status to beta.)
Regard
Kurt
P.S.: Just for curiosity: May I ask you which country you are
coming from?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1177810&group_id=48863
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click