Issue Details (XML | Word | Printable)

Key: SWINGX-350
Type: New Feature New Feature
Status: Open Open
Priority: Minor Minor
Assignee: kleopatra
Reporter: janaudy
Votes: 9
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
swingx

Support for fixed columns in JXTable

Created: 19/Jul/06 03:07 AM   Updated: 12/Feb/13 02:44 PM
Component/s: Table
Affects Version/s: 0.9.0
Fix Version/s: None

Time Tracking:
Not Specified

Environment:

Operating System: All
Platform: All

Issue Links:
Dependency
 
Duplicate
 

Issuezilla Id: 350
Tags:
Participants: janaudy, kleopatra, rah003 and Spinnifex


 Description  « Hide

There is a need to support fixed or sticky columns on the left of a table.
The columns defined as fixed must not be scrolled horizontally; the remaining
columns on the right can still be scrolled horizontally.
There is a real need for this in commercial applications, such as financial
electronic trading applications, hence P1.



kleopatra added a comment - 26/Jun/07 08:26 AM

doing this in any way other than a dirty hack is a mayor non-trivial addition.

Started a thread to collect ideas:

http://forums.java.net/jive/thread.jspa?threadID=28000&tstart=0


rah003 added a comment - 20/Oct/07 09:30 AM

Wouldn't it be easier to have fully fledged grid (JXGrid ?) component for this
rather then continuing this endless loop of hacking JTable into something it was
so obviously not designed to be? As much as I would like to see this fixed, I'm
afraid that in the short term it is not likely to happen. Since this is not a
blocker in terms of crashing application, etc. I'm changing priority to P2.


kleopatra added a comment - 23/Oct/07 02:09 AM
      • Issue 617 has been marked as a duplicate of this issue. ***

kleopatra added a comment - 15/Nov/07 07:13 AM


postponed


Spinnifex added a comment - 12/Feb/13 02:08 PM

I agree. Maybe if embedded in a JScrollPane by default -> so more a new JScrollPane?


kleopatra added a comment - 12/Feb/13 02:42 PM

the ultimate problem is making the navigation behave: for users, it should not matter whether they start at a fixed column or any other. That's hard to impossible to get done with two components (like two tables in a scrollpane).

The other way round (show one table and let the viewport do some intelligent mapping) doesn't work at all - it simply isn't meant to be used that way)


kleopatra added a comment - 12/Feb/13 02:44 PM

reduced priority - it will not happen in any foreseeable future, sorry