PriorityRecordsing resets <conflicts> every time

[capone]

It's driving me nuts. I keep changing <Conflicts>Delete</Conflicts> to <Conflicts>Keep</Conflicts>, and it keeps changign back. It's not runnign CDK, or opening/closing GB config.

How can I make this stick?

[KingArgyle]

I'll check the Config section of the RecordingUtils.dll file, and see what is going on, and also make sure that I don't have anything hard coded for when it is saving the entries.

I'm close to releasing a way to manage CDK Scheduler through the web admin as well.

[capone]

It's wierd becuase I can't pin down when it happens. So far, since my last resetting of it manually, it has not changed on open/close of the CP, GB, or after a EPG update. Only things I haven't done is add/edit/or remove a recording, had one happen, or restart.

Anyway, thanks for looking into it, and I'll let you know if I can pin down when it happens.

[KingArgyle]

The only time it should ever happen is when you add/edit/delete a recording from the Scheduler option. That is the only time that the PriorityRecordings.xml is updated. I should be able to simulate this through the new web interface.

[capone]

That is when it's happening. Maybe it's only when doing Power update or whatever it is. You can see the setting on the deatil before you edit, but you can't change it under eidt. The default must be getting reset.

If I put a 2nd occurance of it, below the one that top, would it reset both? Does it do linear read, and would it use the 2nd one, if the first had the opposite direction?

[KingArgyle]

The PriorityRecording.xsd will flag the PriorityRecordings.xml file as invalid if you try to add another Conflicts element. I'm working on the code the method that XRecord calls from RecordingUtils.dll that does the actual saving, so I'll see if I can find the issue there.

[capone]

Heh...yeah, I found that out last night

[KingArgyle]

I think I found the problem. When XRecord retrieves the Priority Recordings, it doesn't get the Config elements, so I made a change that when XRecord or any program instatiates the class used for managing the priority recordings, it will load up the configuration items. If the config items weren't loaded they were taking the default action of "Delete" for conflicts.

I'll post an updated DLL you can try in the next day or so.

[KingArgyle]

Capone, try this version of RecordingUtils.dll. It should take care of your problem.

[capone]

That's great...thx. I'll let you know how it goes.