Hi, To answer your questions:
1. Yes, this is desired behaviour. The intention is to allow different different logs to be analysed at the same time. Very useful when trying to analyse a distributed application. 2. I would prefer to set them globally. I would rather wait to see if the required complexity to implement them a per file basis is really required. I can see a lot of confusion to the users if they are not global. Please send the diffs to me. I'll be happy to review and commit them. Cheers, Oliver > -----Original Message----- > From: Raymond DeCampo [mailto:[EMAIL PROTECTED]] > Sent: Thursday, 20 February 2003 11:07 > To: Log4J Developers List > Subject: Chainsaw and multiple files > > > All, > > I noticed that when you load multiple files with chainsaw that the > effect is cumulative, i.e., logging events from all the files are > simultaneously loaded. I am in the process of creating a recent files > menu and I was going to save the state of the filters for each file. > However, given the current behavior, that doesn't seem to fit. So: > > 1. Is this the desired behavior? > 2. Assuming it is, does it make sense to store the state of the filters > on a per file basis? I.e., I was going to reset the values of the > filters when you load a file you have loaded previously to the values > you previously had. Alternatively, I could just save the filter values > globally. > > I should have something to submit this weekend (including saving column > widths, a recent files menu, perhaps even column visibility and order). > Who should I send the diffs to? > > Thanks, > Ray > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
