[ xframe-Bugs-1177810 ] setSelectionModel just sets frozenTable's

"SourceForge.net" <[email protected]> Wed, 18 May 2005 17:13:26 -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 (Settings changed) 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: Closed
Resolution: Fixed
Priority: 5
Submitted By: Iñaqui Medina (inaquimj)
Assigned to: Iñaqui Medina (inaquimj)
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: Iñaqui Medina (inaquimj)
Date: 2005-04-06 23:29

Message:
Logged In: YES 
user_id=1086927

Hi,

   I am planning to use it in a production system that will not 
be released in a couple of months (it's not even alpha). I have 
tested it and only found the problems I have posted here. I 
have fixed them all and worked arround the first one (I don't 
set the model twice).

  I had done a similar table in a very very similar way myself 
and ran into (and fixed) the problems I'm posting here myself. 
I decided to use yours since it doesn't have 2 problems mine 
had: can resize the last frozen column and you can select 
rows and scroll the frozen table properly.

   So far (other than the problems I've posted) looks very 
stable to me. I've tested it with different tables (I even have 
tree-tables) different column sizes and a fair ammount of data 
in them and works fine. Sometimes Java is slow enough so 
you see a diference when selecting in one KTable before it 
applies in the other.

   I like this approach (that's why I was using it myself) the 
only MAJOR disadvantage is that it doesn't inherit from 
JTable making me change old code to ugly stuff like:

if (comp instanceof JTable)
    ((JTable)comp).someMethod();
else if (comp instanceof JXTable)
    ((JTable)comp).sameMethod();

   But I know there's no way arround it since Java sucks and 
didn't apply multiple inheritance (notice I'm a C++ lover 
myself :))

   Bottom line, JXTable is stable enough and, if you fix what 
I've posted, I think you can set it to beta test state (I don't 
know about the other projects... only used JXTable myself).

   Ah, and I'm from Mexico... you?

----------------------------------------------------------------------

Comment By: Iñaqui Medina (inaquimj)
Date: 2005-04-06 23:07

Message:
Logged In: YES 
user_id=1086927

Hi,

   I am planning to use it in a production system that will not 
be released in a couple of months (it's not even alpha). I have 
tested it and only found the problems I have posted here. I 
have fixed them all and worked arround the first one (I don't 
set the model twice).

  I had done a similar table in a very very similar way myself 
and ran into (and fixed) the problems I'm posting here myself. 
I decided to use yours since it doesn't have 2 problems mine 
had: can resize the last frozen column and you can select 
rows and scroll the frozen table properly.

   So far (other than the problems I've posted) looks very 
stable to me. I've tested it with different tables (I even have 
tree-tables) different column sizes and a fair ammount of data 
in them and works fine. Sometimes Java is slow enough so 
you see a diference when selecting in one KTable before it 
applies in the other.

   I like this approach (that's why I was using it myself) the 
only MAJOR disadvantage is that it doesn't inherit from 
JTable making me change old code to ugly stuff like:

if (comp instanceof JTable)
    ((JTable)comp).someMethod();
else if (comp instanceof JXTable)
    ((JTable)comp).sameMethod();

   But I know there's no way arround it since Java sucks and 
didn't apply multiple inheritance (notice I'm a C++ lover 
myself :))

   Bottom line, JXTable is stable enough and, if you fix what 
I've posted, I think you can set it to beta test state (I don't 
know about the other projects... only used JXTable myself).

   Ah, and I'm from Mexico... you?

----------------------------------------------------------------------

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


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click