Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-4314209

JTable: cell-[range-]selection problems in kestrel-rc1 (see SwingSet2)

    XMLWordPrintable

Details

    • beta
    • generic, x86
    • generic, windows_nt

    Description



      Name: krT82822 Date: 02/19/2000


      prev synopsis: "simple JTable bug when CTRL pressed and cell selected. (SwingSet2.jar demo)" [already edited once]

      java version "1.3.0rc1"
      Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0rc1-T)
      Java HotSpot(TM) Client VM (build 1.3.0rc1-S, mixed mode)

      Hi, I found a strange behavior on JTable. I have already posted on the forums
      and people have noticed that it happens on JDK1.2.2 too (tks dupontv!!).
      I searched the bug database and haven't found anything...

      How to reproduce:
      1 - Install the last jdk1.3 release candidate
      2 - run SwingSet2.jar demo
      3 - click on JTable demo
      4 - ensure that both 'row selection' and 'column selection' are anabled
      5 - click on cell [1,1] (first row, first col)
      6 - press CTRL and hold
      7 - click on cell [3,1] (third row, first col)

      You will see that the selections disappear...
      If you use getSelectedIdex you will get them, but they are not shown...
      It works fine (kind of) if you click on cell [1,1] and then
      on cell [3,n] (n!=1)
      (Review ID: 100668)
      ======================================================================

      Name: krT82822 Date: 02/19/2000


      java version "1.3.0rc1"
      Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0rc1-T)
      Java HotSpot(TM) Client VM (build 1.3.0rc1-S, mixed mode)

      We have an application that utilizes a number of JTables. In one particular
      area, the JTable has a number of active cells filling the top few rows of the
      JTable, and non-active, greyed-out rows of cells below. With 1.3RC1 (and
      1.3Beta), selecting a cell in the "active" region will cause cells in the
      inactive region to be redrawn in white.

      This appears to be benign --- there are no other side effects noticeable. It's
      just annoying from a visibility standpoint.

      At this point, I don't have a small set of code that reproduces this. I'll try
      to get this soon, however (deadlines, deadlines!)
      (Review ID: 101134)
      ======================================================================

      Attachments

        Issue Links

          Activity

            People

              busersunw Btplusnull User (Inactive)
              kryansunw Kevin Ryan (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                Imported:
                Indexed: