[mythtv] conflict resolution

[Bruce Markey]

David Engel wrote:
...
> Implements the recordoverride logic, more or less, like I proposed
> eariler.  The main difference from earlier is that it does not remove
> items from the potential recording list.  This was needed for the next
> change.

Outstanding! After fixing a couple typos (see below) I was able
mark episodes "Don't record it" and get the correct results
from the scheduler. What's really impressive is marking a later
episode as "Record it anyway" and seeing the earlier showing
change status to "4" (nrOtherShowing) just as you had described.

I look forward to making "NBA Basketball" a record anywhere
and marking out the games I know I won't watch ;-)

> Adds some extra fields to programinfo to make it easier and,
> hopefully, more effiecient to get recording type and accurate
> conflict/will/won't record info when displaying program guide data.
> Proglist uses this to show when a program conflicts or will/won't
> record.

I think the NoRecordType is a marvelous idea, makes perfect
sense and can be very useful down the line. Good job!

> Adds control of recordoverrides in viewscheduled.  With a little more
> work most of this control could be moved to programinfo so it would be
> available from other places, eg. guidegrid, proglist, etc.  Because of
> an earlier change, more "not" recordings will show up in
> viewscheduled.  If that's not desired, I can add code to filter them
> out.

That commercial DVR that puts the list of showings on a separate
page than the scheduled recordings drives me nuts. Having them
all on the same page but distinguished by color is just great.
Listing all the "not" recordings makes sense with the ability
to override and the override page including the explanation
of why it isn't scheduled. I do want to see these but I can
also understand wanting to trim it to just the things that will
be recorded. Maybe add keys like 1 for all conflicts 2 scheduled
recordings like the sort choices on the Rankings page.

> One thing this patch does not do yet is gracefully handle the case
> where a program is covered by multiple scheduledrecordings.  For
> example, if a program is covered by a SingleRecord and an AllRecord,
> they will show up as conflicting.  The previous code looks like it
> tried to handle this but it didn't appear to work and wasn't complete
> enough anyway.  I will fix this soon.

Thanks, it should probably prune the recurring item if there is
a single item for the same showing.


I did have to fix a couple little things. The table CREATE failed
due to a misplaced comma and nrLowerRanking had a negative value.
Attached is a diff against the patchfile.

--  bjm

-------------- next part --------------
--- /tmp/override.patch	2003-11-05 15:30:31.000000000 -0800
+++ override.patch	2003-11-05 17:47:22.000000000 -0800
@@ -29,7 +29,7 @@
 +"   starttime TIMESTAMP NOT NULL, "
 +"   endtime TIMESTAMP NOT NULL, "
 +"   title VARCHAR(128) NULL, "
-+"   subtitle VARCHAR(128) NULL ",
++"   subtitle VARCHAR(128) NULL, "
 +"   description TEXT NULL "
 +");",
 +""
@@ -313,7 +313,7 @@
 +    nrOtherShowing = 4,
 +    nrTooManyRecordings = 5,
 +    nrDontRecordList = 6,
-+    nrLowerRanking = -7,
++    nrLowerRanking = 7,
 +    nrManualConflict = 8,
 +    nrAutoConflict = 9
 +};