[mythtv-commits] Re: Ticket #643: Program matching multiple recording schedules behaves unexpectantly

[MythTV]

#643: Program matching multiple recording schedules behaves unexpectantly
-------------------------------+--------------------------------------------
 Reporter:  mythtv at hburch.com  |        Owner:  gigem  
     Type:  defect             |       Status:  closed 
 Priority:  minor              |    Milestone:  unknown
Component:  mythtv             |      Version:  head   
 Severity:  medium             |   Resolution:  fixed  
-------------------------------+--------------------------------------------
Changes (by bjm):

  * resolution:  => fixed
  * status:  new => closed

Comment:

 (In [8191]) Closes #643

 In cases where two recording rules match the same showing, one
 of them needs to take precedence. An rsRepeat or rsInactive will
 not be considered for recording so we penalize these to force
 them to yield to a rule that may record. Otherwise, more
 specific record type beats less specific.

 The patch suggests priority as a factor but neither gigem or I
 are comfortable with this. The controlling rule could flip-flop
 when changing a priority on a different showing for a different
 reason. Also, it is unknown if there would mysterious behavior
 due to the total priority calculations (input preference, channel
 priority) that may lead to unexpected results. Therefore, this
 will not go in unless someone can make a very compelling argument
 for it.

-- 
Ticket URL: <http://cvs.mythtv.org/trac/ticket/643>
MythTV <http://www.mythtv.org/>
MythTV