I am thrilled to see progress on the table model.
As for the CyclicBuffer you could use two cascading cyclic buffers. One buffer for storing events as they arrive and a second one for the events retained after filtering. The gui table would only use the second table to display events. The first one is used only as a cache to repopulate the second buffer when the filtering rules change. Does it make sense?
At 06:49 AM 5/26/2003 +0000, you wrote:
psmith 2003/05/25 23:49:04
Modified: src/java/org/apache/log4j/chainsaw CyclicBufferList.java
Added: tests/src/java/org/apache/log4j/chainsaw
CyclicBufferListTest.java
Log:
fixed a couple of issues in the CyclicBufferList and added a Test case class.
Certainly wouldn't want to be relying on CyclicBufferList as part of Life support systems at this point...
Revision Changes Path
1.2 +62 -9 jakarta-log4j-sandbox/src/java/org/apache/log4j/chainsaw/CyclicBufferList.java
--
Ceki For log4j documentation consider "The complete log4j manual"
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
