Incorrect Description Of Recurring Recordings

[mvallevand]

It still wants 1.0.66

Martin

[toricred]

Any updates on this?

[sub]

Try this one.

[mvallevand]

Try this one.

Thanks, that fixes the version problem but the update of the Recording Directory that UJB wrote you about still takes two attempts.

To reproduce:

- create a recurring recording with the default directory
- edit a recurring recording and change the directory to non-default. This creates a blank <RecordingDirectoryID></RecordingDirectoryID> entry in match_rules
- after that the next update works (but the scheduled recordings won't be updated until the next full update)

Martin

[toricred]

Well, at least NRecord started with this one. I'm sure it's good to go now. Thanks.

[sub]

Thanks, that fixes the version problem but the update of the Recording Directory that UJB wrote you about still takes two attempts.

To reproduce:

- create a recurring recording with the default directory
- edit a recurring recording and change the directory to non-default. This creates a blank <RecordingDirectoryID></RecordingDirectoryID> entry in match_rules
- after that the next update works (but the scheduled recordings won't be updated until the next full update)

Martin

I haven't had time to look into this yet. It's not a problem introduced by this updated NUtility.dll though - it sounds like it's always been that way.

[mvallevand]

I haven't had time to look into this yet. It's not a problem introduced by this update NUtility.dlls though - it sounds like it's always been that way.

Ok I thought I had tested this before but maybe I hadn't noted the pattern and blamed the first fail on user error.

Martin

[georgewbateman]

Thank you.

I checked Recurring Recordings, Details Popup and NEWA. Much, much better. The previous display was very confusing. The information by NEWA is unchanged. I am assuming that NEWA is not affected by these changes. (Someones else's responsibility ?)

As I am sure you know that what shows are scheduled can be dependent on the date and time the recurring recording is initiated. (If for example a show appears every Monday and is about to aired on the 1st, 8th and 15th, if the recurring recording is initiated from the airing on the 8th then the airing on the 1st will NOT be recorded.) For someone new to NextPVR, this behavior is confusing when you are expecting ALL to really mean ALL. Adding the additional information of the date and time recording are to begin would eliminate this confusion.

[sub]

Thank you.

I checked Recurring Recordings, Details Popup and NEWA. Much, much better. The previous display was very confusing. The information by NEWA is unchanged. I am assuming that NEWA is not affected by these changes. (Someones else's responsibility ?)

Great. Yes, UJB would need to make change to NEWA. He can use the builtin description function for getting the same description as NextPVR generates though.

As I am sure you know that what shows are scheduled can be dependent on the date and time the recurring recording is initiated. (If for example a show appears every Monday and is about to aired on the 1st, 8th and 15th, if the recurring recording is initiated from the airing on the 8th then the airing on the 1st will NOT be recorded.) For someone new to NextPVR, this behavior is confusing when you are expecting ALL to really mean ALL. Adding the additional information of the date and time recording are to begin would eliminate this confusion.

Yes, the behaviour is intentional. I'll look into adding this extra info about it in the UI if it can be done without adding too much clutter.

[mvallevand]

Thanks, that fixes the version problem but the update of the Recording Directory that UJB wrote you about still takes two attempts.

To reproduce:

- create a recurring recording with the default directory
- edit a recurring recording and change the directory to non-default. This creates a blank <RecordingDirectoryID></RecordingDirectoryID> entry in match_rules
- after that the next update works (but the scheduled recordings won't be updated until the next full update)

Martin

Sub provided an update for testing that fixes these problems and since he is away he agreed to let me post it.

Martin