[mythtv-commits] Ticket #3448: "Upcoming Recordings" in MythWeb does not properly display adjusted times for recordings that begin/end early

[MythTV]

#3448: "Upcoming Recordings" in MythWeb does not properly display adjusted times
for recordings that begin/end early
-----------------------+----------------------------------------------------
 Reporter:  anonymous  |        Owner:  kormoc    
     Type:  defect     |       Status:  closed    
 Priority:  minor      |    Milestone:  0.22      
Component:  mythweb    |      Version:  0.20-fixes
 Severity:  medium     |   Resolution:  wontfix   
  Mlocked:  0          |  
-----------------------+----------------------------------------------------

Comment(by Nick Morrott <knowledgejunkie (at) gmail (dot) com>):

 Replying to [comment:7 kormoc]:
 > I understand the concern, but I'm sure we'd get more bugs if we had a
 list like
 >
 >  * 10am to 11 am - Show X - Airtime 10 Am, 1 hour
 >  * 11 am to Noon - Show Z - Airtime 3 Pm,  1 hour
 >  * Noon to 1 pm  - Show Y - Airtime Noon,  1 hour
 >
 > That makes no sense to me at all.
 >
 > Does it to you?

 Looking at the same listing in mythfrontend, there is no specific
 reference to airtime in the main listing - it lists only the scheduled
 title, channel, (amended) recording time, and input. Because this data
 comes out of the scheduler, which will have taken any user-overridden
 start/stop times into account (the crux of this issue), I still argue that
 any interface to this data should be consistent in the way it is
 displayed, for the ultimate benefit of the user.

 I haven't seen any tickets reporting confusion with this listing in
 mythfrontend, perhaps because the only time you'll see 'odd' timings is
 when the user has /specifically/ overridden the schedule timings with
 their own hard start/stop early/late, and perhaps because it displays the
 information that most users would expect? When a user does provide a
 timing override, the fact the MythWeb listing does not update to reflect
 equally could generate confusion in MythWeb, and is clearly the basis of
 this ticket.

 I've always understand the 'Upcoming Recordings' page to show /when/ the
 actual scheduled recordings will be made (per the scheduler), and on what
 tuner. I can quickly see whether any specific timings have taken effect
 (as you can in mythfrontend), and can do this via a browser whilst being
 distant from mythfrontend. It should agree with the output of mythbackend
 --printsched.

 There is also the reported inconsistency in MythWeb itself, between
 Upcoming Recordings and Backend Status->Schedule, with the latter giving
 the adjusted start time as mythfrontend's Upcoming Recordings and
 --printsched do, but the former not. Are these supposed to show the same
 data (upcoming scheduled recordings) or not?

 Getting across any differences between 'Scheduled Recording Time' (when
 your machine will actually record the programme) and 'Airdate' (when the
 listings show the programme as being broadcast) to the user, especially in
 scenarios where there are differences, requires consistency across the
 MythTV stable.

 Content-wise, I don't see any reason why MythWeb's Upcoming Recordings
 page cannot mirror that of mythfrotend or --printsched, apart from the
 wording used to describe the programme timings. Perhaps we could use a
 different CSS class for upcoming recordings which have overridden timings,
 to make it clearer? Are there any architectural reasons why the same
 information cannot be shown in MythWeb?

 Isaac/other devs/users: do you have view on this? Have I missed the point
 here?

-- 
Ticket URL: <http://svn.mythtv.org/trac/ticket/3448#comment:8>
MythTV <http://www.mythtv.org/>
MythTV