DVR autorec: use 'Start After' and 'Start Before' for the start time window

This commit is contained in:
Jaroslav Kysela 2014-12-26 16:07:21 +01:00
parent e2bd233a4f
commit 75fb7a929d
2 changed files with 6 additions and 6 deletions

View file

@ -79,13 +79,13 @@ The maximal duration of a matching event - in other words, only match programmes
<dd>
On which specific days of the week to find matching programmes.
<p>
<dt><b>Start Time</b>
<dt><b>Start After</b>
<dd>
An event which starts between this "start time" and "start time up to" will be matched (including).
An event which starts between this "start after" and "start before" will be matched (including boundary values).
<p>
<dt><b>Start Up To</b>
<dt><b>Start Before</b>
<dd>
The start up to limit.
An event which starts between this "start after" and "start before" will be matched (including boundary values).
<p>
<dt><b>Priority</b>
<dd>

View file

@ -876,7 +876,7 @@ const idclass_t dvr_autorec_entry_class = {
{
.type = PT_STR,
.id = "start",
.name = "Start Time",
.name = "Start After",
.set = dvr_autorec_entry_class_start_set,
.get = dvr_autorec_entry_class_start_get,
.list = dvr_autorec_entry_class_time_list_,
@ -885,7 +885,7 @@ const idclass_t dvr_autorec_entry_class = {
{
.type = PT_STR,
.id = "start_window",
.name = "Start Up To",
.name = "Start Before",
.set = dvr_autorec_entry_class_start_window_set,
.get = dvr_autorec_entry_class_start_window_get,
.list = dvr_autorec_entry_class_time_list_,