[mythtv] [mythtv-commits] Ticket #292: "Never Record" in Scheduled Recordings doesn't always work.

Tom Metro tmetro+mythtv-dev at gmail.com
Fri Apr 13 22:42:19 UTC 2007

Janne Grunau wrote:
> And your wrong then you say "never record" doesn't work, it does work.

Correct. It works intermittently. But isn't that how it is described in 
the ticket? I retained the original title on the new ticket I opened, 
which says "doesn't always work."

> But there is very little that can be done.
> Inposing a multiple seconds long delay until the backend has finished 
> the reschedule is at least as bad as the current behaviour.

Agreed. And in the end that may be the case, now that I understand the 

I did list several possibilities in the new ticket:

One possibility I didn't fully articulate in the ticket is that if you 
know you've just changed the "never record" flag for an episode, the 
code could sit in a pooling loop waiting for that to change, with some 
timeout limit. That way if the scheduler is fast it returns immediately.

Delays are never ideal, but ones that work only some of the time aren't 
good, and situations that result in wrong information being shown are 
even worse.

The worse part of this bug is that it provides misleading information to 
the user that directly contradicts the action they just took. Even if 
there was some way to tell that the "MythTV Status" field was in an 
indeterminate state and indicate that on the page, it'd be an improvement.


Tom Metro
Venture Logic, Newton, MA, USA
"Enterprise solutions through open source."
Professional Profile: http://tmetro.venturelogic.com/

More information about the mythtv-dev mailing list