Reply to thread

Message

<blockquote data-quote="dvdfreak" data-source="post: 169184" data-attributes="member: 21313">What I have at the moment is that the scheduler will remember any episode title it records for a scheduled program.&nbsp; There will then be a rule to not re-record anything with the same episode title twice.This is not built in at the moment, and in a way, this can never be done by the scheduler on its own, since it doesn't know if something has been watched.&nbsp; But I could provide a method to remove an episode from the recorded list, so point 2 is also easy to implement.This one is trickier, since the scheduling subsystem doesn't know anything about conflicts.&nbsp; The design is to get a good rule-based scheduling engine, actually recording anything is one level higher up.&nbsp; Perhaps this is something that will need to be revisited later on, but then the scheduling service would have to know about what cards can record what, etc...&nbsp; And currently this is out of scope.However, with the appropriate methods on the scheduler API we could provide this I think.&nbsp; Somehing like a GetAllEpisodeReruns() method to provide the recording/conflicts engine with all possible reruns so it can decide what to do.Thanks for the valuable input!</blockquote>

[QUOTE="dvdfreak, post: 169184, member: 21313"] What I have at the moment is that the scheduler will remember any episode title it records for a scheduled program. There will then be a rule to not re-record anything with the same episode title twice. This is not built in at the moment, and in a way, this can never be done by the scheduler on its own, since it doesn't know if something has been watched. But I could provide a method to remove an episode from the recorded list, so point 2 is also easy to implement. This one is trickier, since the scheduling subsystem doesn't know anything about conflicts. The design is to get a good rule-based scheduling engine, actually recording anything is one level higher up. Perhaps this is something that will need to be revisited later on, but then the scheduling service would have to know about what cards can record what, etc... And currently this is out of scope. However, with the appropriate methods on the scheduler API we could provide this I think. Somehing like a GetAllEpisodeReruns() method to provide the recording/conflicts engine with all possible reruns so it can decide what to do. Thanks for the valuable input! [/QUOTE]

Verification