> However (considering the bug fixed for the collapsed thread display), breaking the thread is not a confortable solution. 

Well, but it's the only way which gives you a 1:1 correlation between what you filter and what you see below. If you want to 
see the full thread for an entry which gets shown after you apply a filter, just click on that entry, and you will be taken to 
the single entry display which shows the full thread on top of it. This is the only way I can keep search results consistent, 
so I would rather like to keep it like this.

Hello,

  I gave it a try. See: https://midas.psi.ch/elogs/Forum/66690

Gabriele

Hello,
   I gave it a try using the svn version n. 2283 (12 Jan 2010).  The threaded display can be collapsed only if you don't 
apply any sorting. In the latter case, if you sort in some way ( with "Sort Attributes =" or "sort=" in the url), the 
thread cannot be collapsed anymore.

Also if I apply any filter from the quick filter bar, I cannot collapse the thread anymore (also without sorting). 

As example, these are the numbers of entries I obtain with my logbook :

  http://localhost:8080/mylogbook/?mode=threaded&expand=0     => 75 entries (OK)
  http://localhost:8080/mylogbook/?mode=threaded&expand=0&sort=EventID  =>  445 entries  (WRONG it should collapsed)
  http://localhost:8080/mylogbook/?mode=threaded&expand=0&Interaction=nuCC   => 335 entries 

However (considering the bug fixed for the collapsed thread display), breaking the thread is not a confortable solution. 
I choose to show the logbook in the threaded mode, because I'm interested in grouping the entries in threads. 
In my opinion, this feature is good (and it is my favourite) and should be preserved despite any sorting or filtering. 
This is why I suggest to ask to the user which entries (first or last) better applies for sorting and filtering. 

Ciao

   Gabriele


> You are absolutely right. When doing filtering, entries shown or not shown have not much to do with the filter. 
> Rather than messing around with first and last entries, I decided to break apart threads completely when doing 
> filtering, so the entries are treated as individual entries, just like what you do when filtering in summary mode. 
> This gives then consistent filtering results. The modification is done in revision 2282.

 Here is the mail log:

Jan 12 13:51:54 techies lmtpunix[3184]: dupelim: eliminated duplicate message to user.jf id <neteng-1067@emich.edu> (delivery)

The message id we are experiancing problems with is in the header;

Message-ID: <neteng-1073@emich.edu>

Thank you for the help.

Actually what you report is a bug. The filtering does not work in threaded display mode, only in summary and full. I fixed that bug in the current SVN version, so if you download and compile it, you can give it a try. The fix will be contained in the next official release.

 Sorry for my english. In fact, i found the answer by myself. But I ll explain to you.

in attachement 1, a small part of our ELOG. When I choose FBT in the quick filter "groupe incriminé". Elog respond that there is no entrie found (attachement 2)

But, with the find function, when i select display full entries and FBT in "groupe incriminé", Elog show the entrie ( attachement 3).

I found the answer. In fact, Elog respond no entrie when threaded is selected. I have to choose Full or summary for that working.

sorry

Xavier

I don't understand your questions. Can you please give an example. 

Hello,

We would like to use more the quick filter command on attributes.

On the other hand, when we use it, the result does not displaying entries which are in answer of another attribute. Is there a command which allow that possibility like when we select display full entries in the search mode?

Thanks in advance

Xavier