Changes between Initial Version and Version 1 of Ticket #2070


Ignore:
Timestamp:
Jul 18, 2006, 3:47:04 PM (18 years ago)
Author:
Robert Tsai
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #2070 – Description

    initial v1  
    33The MythWeb search results ("Movies", "New Titles", etc.) show the titles on these overlapping channels as separate results. However, I'm not sure of the best way to handle this.
    44
    5 I've attached a patch that groups the results by channum, so the interface gets less cluttered. However, this might not be the "best" way to handle this scenario. Taking the "movies" canned search as an example, I generally use "Find one showing", and things work as expected and as intended; the GROUP BY channum doesn't hurt anything.
     5I've attached a patch that groups the results by channum, so the interface gets less cluttered. Taking the "movies" canned search as an example, I generally use "Find one showing", and things work as expected and as intended; the GROUP BY channum doesn't hurt anything.
    66
    7 However, select "Record just this showing" might be intended to mean "record from this card", which would be hidden by any channum GROUP BY clauses.
     7However, selecting "Record just this showing" might be intended to mean "record from this card", which would be hidden by any channum GROUP BY clauses.
    88
    9 I haven't checked the backend scheduler code to see exactly what "Record this showing" means yet.
    10 
    11 I've attached the patch I use in my tree in case anyone has the same peeve, but I'm not quite sure this should be committed.
     9I haven't checked the backend scheduler code to see exactly what "Record this showing" means yet. I've attached the patch I use in my tree in case anyone has the same peeve, but I'm not quite sure this should be committed.