1

I ran into this bug in Oracle's JDK 7 for OS X: Spurious calls to setValueAt with JTables in Java 7 on OS X Lion? The quick summary is that when you use the arrow keys to navigate through a JTable, setValueAt() gets called with empty strings. It's kind of disconcerting to watch your data disappear as you move through the table.

It is still unfixed, and Oracle has vanished the bug report that I filed. How can I work around this?

Ideally, I'd like it to simply not call setValueAt() at the wrong times, but if that can't be the case, I'd like find a work around that would allow the code in setValueAt() to understand that it has been called with no real edits made.

Unfortunately, I don't understand the workings of the events/methods in a JTable. So here is my (unfortunately vague) question. How can I work around this?

Community
  • 1
  • 1
BillRobertson42
  • 12,602
  • 4
  • 40
  • 57
  • I added an answer in your other question. I can work around the `setValueAt` issue but have other issues ... seems like JDK7 has a few bugs in it. As mentioned in my answer there, I do not see data disappearing but I do see the calls to `setValueAt` which should't be needed – Robin Nov 15 '12 at 22:57
  • @Robin I feel it's more of a follow up. – BillRobertson42 Nov 15 '12 at 23:42

0 Answers0