Why does fireTableDataChanged cause getValueAt called repeatly?

[Allen]

First update table model.
tableModel.addData()...

Then update table display.
tableModel.fireTableDataChanged()...

I found getValueAt called repeatly.
Is there anything wrong?

 

[Tom Hawtin]

First update table model.
tableModel.addData()...

Then update table display.
tableModel.fireTableDataChanged()...

I found getValueAt called repeatly.
Is there anything wrong?

You have fired the event that says that all the data in the table has
changed. Anything interested in the table data (for instance the JTable
rendering the data) will have to reread all the relevant data.

Tom Hawtin

 

[Allen]

You have fired the event that says that all the data in the table has
changed. Anything interested in the table data (for instance the JTable
rendering the data) will have to reread all the relevant data.

Tom Hawtin

Thank you!

The table just shows log items. When a new log comes up, it will be
inserted
at the first row. So I call fireTableDataChanged method.

How to avoid repeatly calling getValueAt?

 

[Tom Hawtin]

The table just shows log items. When a new log comes up, it will be
inserted
at the first row. So I call fireTableDataChanged method.

How to avoid repeatly calling getValueAt?

Using fireTableRowsInserted would produce a more precise event.

Probably the visible section of the table will be reread anyway. If it's
a performance problem, cache your table values.

Tom Hawtin

 

[Allen]

Using fireTableRowsInserted would produce a more precise event.

Probably the visible section of the table will be reread anyway. If it's
a performance problem, cache your table values.

Tom Hawtin

Now I use fireTableRowInserted method. It also calls getValueAt
endlessly.
I only add two rows into the table. Look these output message.
........................................................................

 

[Tom Hawtin]

Now I use fireTableRowInserted method. It also calls getValueAt
endlessly.
I only add two rows into the table. Look these output message.

Literally endlessly? Are you sure you are not causing the table model to
fire events from getValueAt or causing repaints/revalidates in some
other way?

Tom Hawtin

 

[Allen]

Literally endlessly? Are you sure you are not causing the table model to
fire events from getValueAt or causing repaints/revalidates in some
other way?

Tom Hawtin

Sorry. I found the reason now. I used my custermized multiline
textarea cell renderer.
And I just overrided getTableCellRendererComponent method of
TableCellRenderer interface.
Now I change to use TextAreaRenderer download from
http://www.javaspecialists.co.za/archive/newsletter.do?issue=106&locale=en_US.
It is ok now.

Thank you!