Bug 309956 - Logviewer search is not helpful, does not show dates that match
Summary: Logviewer search is not helpful, does not show dates that match
Status: RESOLVED FIXED
Alias: None
Product: telepathy
Classification: Frameworks and Libraries
Component: log-viewer (show other bugs)
Version: 0.5.0
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: Future
Assignee: Telepathy Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-12 12:10 UTC by Bernd Buschinski
Modified: 2013-02-14 18:44 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 0.6.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bernd Buschinski 2012-11-12 12:10:56 UTC
I have a friend with I chat daily, so the log are present everyday and always long.

I know he wrote "example text" once, so lets use the logviewer and search for it..
So I typed "example text" in the search all logs inputline.

All that did was reduce the contacts that did write it, as I already know it was my friend this was not helpful sofar. Even worse all dates in the calendar are still blue. And the worst, the current "chatwindow-log" was empty, it only pointed me to a previous conversation, which was also empty... and so on.
As I clearly could not remember the date when he wrote "example text" .. I am lost here.

The logviewer search did not help at all.
I suggest listing all dates that matches rather than a calendar. Even if all dates are marked in the calender it would still requiere me to check all month.. which after years is just insane

Reproducible: Always

Steps to Reproduce:
1. open ktp logviewer
2. search "example text"

Actual Results:  
it reduces the contacts that wrote the text

Expected Results:  
it should list all dates that list that wrote the text, not show them in the calender, or only optional
Comment 1 Daniel Vrátil 2012-11-12 16:07:24 UTC
I think I have recently fixed this issue. Could you please either test git master of ktp-text-ui or try to apply the patch in review to current tarball whether it fixes your issue?
Comment 2 Daniel Vrátil 2012-11-12 16:10:32 UTC
This is the review request with the patch: https://git.reviewboard.kde.org/r/107273/