[mythtv] Re: [mythtv-commits] mythtv commit: r7962 by danielk

[Stuart Auchterlonie]

On Mon, Nov 21, 2005 at 03:29:12PM +0000, mythtv at cvs.mythtv.org wrote:
>       Author: danielk
>         Date: 2005-11-21 15:29:12 +0000 (Mon, 21 Nov 2005)
> New Revision: 7962
>    Changeset: http://cvs.mythtv.org/trac/changeset/7962
> 
> Modified:
> 
>    trunk/mythtv/libs/libmythtv/eithelper.cpp
> 
> Log:
> 
> Changes EIT insertion so that if you already have good datadirect info for timeslot it is not replaced with the EIT version.
> 
> It should still catch schedule changes. It will insert the EIT program
> if the title or start/end times are different or if the program subtitle
> exists in the EIT program and it is different from the one in the DB.
> 

I think a better way to do this would be to setup priorities
for EIT information.

There are two basic sources
1. xmltv
2. EIT data

EIT data breaks down to 6 different items
1. Now/Next this network
2. Now/Next other network
3. Days 0-3 EPG this network
4. Days 0-3 EPG other network
5. Days 4-7 EPG this network
6. Days 4-7 EPG other network.

Not all of these are present on all networks / transponders.

If we add an extra column to the program table in the DB, we can
save the information about where it came from to determine the
best source of information.

User level configuration should only be between xmltv & EPG.
The specific EPG levels should be automated in the background.


Don't like this bit much...
// To overwrite datadirect data with eit data use this instead
//  static const QString timeFmtDB2 = "yyyy-MM-ddThh:mm:00";

Rather than having to change the timeFmt, why don't we do a
QRegExp replacement of 'T' to a ' '.


Stuart