Is it just me, or does the current Log4J release, and HEAD do something weird the first time data starts streaming into the TableModel? I find I have to resize the ChainSaw window to get it to revalidate the Container and start displaying the log events.
I've had a similar problem in another Swing app before (this time using JTree) and found I had to force the revalidation of the container. I added a quick TableModelListener to to do a single revalidation of the Container and JTable, the first time the table data changes, but that still doesn't seem to have the desired effect. So I am wondering if it's just my local JDK? Anyone else spotted this effect? (running JDK1.4.0 on W2k). cheers, _________________________ Paul Smith Lawlex Compliance Solutions phone: +61 3 9278 1511 email: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
