Recordings via the IScheduleHelper API

[Ernie-c]

I could of, but I didnt. It achieves the same result.

Using enums you would better support the user of your API, by giving him intellisense, and at the same time avoid impossible values. Using ints I had to find out possible values in the documentation, and couldn't find them.

[sub]

The public API doesnt give you this information, but you can look at the capture_source_oid column of the RECORDING_SCHEDULE table after the recording is complete.

Thanks. Are there any plans to add/extend this API further ?

I have no immediate plans to change this particular part of the public API. I prefer to keep the internals of capture sources etc in the private API.

Using enums you would better support the user of your API, by giving him intellisense, and at the same time avoid impossible values. Using ints I had to find out possible values in the documentation, and couldn't find them.

I'm aware of the differences. The constants work just fine though. Its been this way for three years, and we've never had a problem with them to date, so I dont see any need to change it now.

[whurlston]

If you prefer to use an enum, you can easily construct your own with those int values.

[Ernie-c]

I have no immediate plans to change this particular part of the public API. I prefer to keep the internals of capture sources etc in the private API.

Pitty, because it reduces the functionality and power of the combination of our scheduler with GBPvr as a recorder a lot.

I'm aware of the differences. The constants work just fine though. Its been this way for three years, and we've never had a problem with them to date, so I dont see any need to change it now.

I'm not really having a problem with these ints, I'm only I saying it would be more API-userfriendly.

If you prefer to use an enum, you can easily construct your own with those int values.

True, but then I have to check every new version for possible added / changed enums, while that is the responsibility of the one who writes the API

[whurlston]

Your original question about using enums was in regard to the use of "const int" for the days. I dont think we will be adding any days to the week anytime soon.

[Ernie-c]

Your original question about using enums was in regard to the use of "const int" for the days. I dont think we will be adding any days to the week anytime soon.

But you could add "Weekends", "WorkingDays" for example to the enum ...

[sub]

We dont need to debate this any further. I chose to use constants. I could have used an enum instead, but I didnt. It doesnt really matter in the grand scheme of things. Everyone is welcome to have different personal preferences on coding style.

[Ernie-c]

1) you could call IScheduleHelper.GetListingsForTimePeriod(DateTime. now, DateTime.now). This will return a list of Channel objects, which you can use to get the name and OID.

It works, Thanks !

[Ernie-c]

Hello again,

I have a question about the fileName argument (see below), because no matter what I put in, it seems that the recording filename is always constructed using the programme's Title + "_" + startdate + starttime.
Is that correct ? Is the argument no longer used ?

eg of a recording filename : "Test_20080221000822.mpg"

And what is the purpose of the maxFiles argument ?

ScheduledRecording scheduledRecording = scheduleHelper.SheduleRecording(programme.getChannelOID(),
programme.getStartTime(),
programme.getEndTime(),
programme,
ScheduledRecording.TYPE_RECORD_ONCE,
ScheduledRecording.GROUP_NONE,
fileName,
ScheduledRecording.QUALITY_HIGH,
1,
127, // = "any day"
0,
0);

Thanks.

[sub]

Correct.

The supplied value is only used as part of the final filename when doing a manual recording. (ie, not linked to a programme)