Bug #1705
closed
Search results (in Android client) grouped by channel
Added by riban almost 11 years ago.
Updated almost 11 years ago.
Description
When performing a simple text search, the results are displayed in time order but grouped by channel, e.g.
Channel4+1
1900: The Simpsons
Channel4
1800: The Simpsons
There is an option to chose to sort by time or alphabetically. It is desirable to sort all results by actual time. It may be desirable to optionally group by channel but this does not seem to be the obvious (to me) default option.
Files
I will check thinks. Thanks for feedback
- Assignee changed from herrlado to riban
Can you show me the screenshot of it? Because the evens are sorted by time. But sure your example with Channel 4 and Channel 4+1 would be an error, because the entry with 18:00 must be on earlier, so please make a screenshot of it. Is this always a problem or it occures only sometimes?
And I have checked and it seems the sorting by Alphabet does not realy work or to be more precise, it is not yet implemented.
I have attached a screenshot demonstrating this issue (grouped search results) and issue #1711 (wrong programme details for sequential searches). I can't change assignee back to you.
OK, I think I now what the problem is. I have checked the code and find out, that it seems, that android does not sort the timers at all.
My vdr seems returns them already sorted.
Anyway, Thanks for the screenshot.
- Assignee changed from riban to herrlado
Soloution. There are three options. Sort by Timer, Alphabet and Channel
If you run this search first time and never sorted the list, default is by channel. Then you can switch between
other options and they get persisted, so next time the app know the last decision. But this is not a new feature, this had been introduced in earlier version.
Please test new beta version. It is also published in play store beta version. If you would like to have always the latest build as beta directly from play store
Joins this community
https://plus.google.com/communities/107715366308757458233
and follow the instructions here
https://play.google.com/apps/testing/de.bjusystems.vdrmanager
Agreed - fixed in v12-beta-4.
Redmine configuration has no workflow for reporter to change status of issues so I can't close this issue. I would suggest allowing reporters to at least be able to close and reopen (in progress) resolved issues and change owner of issues with status feedback.
- Status changed from Resolved to Closed
Also available in: Atom
PDF
