Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon1.gif   Collapse to Last and Quick Filter , posted by Gabriele Sirri on Sat Jan 2 01:34:57 2010 example.txtelogd.c.patch
    icon2.gif   Re: Collapse to Last and Quick Filter , posted by Stefan Ritt on Tue Jan 12 09:12:28 2010 
       icon2.gif   Re: Collapse to Last and Quick Filter , posted by Gabriele Sirri on Mon Jan 18 02:13:19 2010 
          icon2.gif   Re: Collapse to Last and Quick Filter , posted by Stefan Ritt on Mon Jan 18 08:18:48 2010 
Message ID: 66670     Entry time: Tue Jan 12 09:12:28 2010     In reply to: 66659     Reply to this: 66690
Icon: Reply  Author: Stefan Ritt  Author Email: stefan.ritt@psi.ch 
Category: Request  OS: Windows  ELOG Version: 2.7.8-2280 
Subject: Re: Collapse to Last and Quick Filter  
> Hello,
>    I feel that the filter result could be confusing and unexpected when "COLLAPSE TO LAST" is enabled: you 
> filter the first entry but you show the last one. What is filtered doesn't correspond with what is shown (look 
> the attached example). 
> 
> I suggest to implement an option to let the user decide which entry (first or last) should be retrieved for 
> filtering (a tentative patch is attached).
> 
> Thank you 
> 
>     Gabriele
> 
> P.S. A similar behaviour occurs when you sort the logbook: it could appear as not sorted because you sort the 
> first entry but the last one is shown.

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.
ELOG V3.1.5-fe60aaf