Advanced Configuration (config.xml)

[imilne]

I've just tried to get this page reasonably back up to date with all the new options that have slipped in over the past few months.

http://www.nextpvr.com/nwiki/pmwiki.php?...n.Advanced

There's still lots of entries with no description (either because I don't know what they do, or I don't know *for sure* what they do), so please help fill in the gaps if you can...

Iain

[steeb]

I've just tried to get this page reasonably back up to date with all the new options that have slipped in over the past few months.

http://www.nextpvr.com/nwiki/pmwiki.php?...n.Advanced

There's still lots of entries with no description (either because I don't know what they do, or I don't know *for sure* what they do), so please help fill in the gaps if you can...

Iain

Keep up the good work Iain

I would help if I could but I am not sure what half of these settings do! And that is worrying from the man that is trying to write a config.xml GUI editor

cheers

steeb

[imilne]

Right, let's try and get through this list, a few per day...

Code:

[B]DeleteAdditionalExtensions[/B]

[I]Stores a list of file extensions that will be used to determine what additional files (if any) will be deleted whenever a recording is removed from disk. [/I]

Is this one correct?

Code:

[B]ScanCollectionMS[/B]

What does this one do? Obviously something at scan time. The time to wait between mutliplex/transponder scans perhaps?

Code:

[B]ScheduleWakeups[/B]

[I]If true, NextPVR will request Windows to wake from sleep or hibernate power states in order to record scheduled EPG events. [/I]

And finally, is this one correct?

Iain

[sub]

To be honest, I dont think you should try to document config.xml. It was never intended to be something was user editable. I change it every release. I'm always adding new settings. Sometimes I'm repurposing old settings. Some of the settings are experimental, and not necessarily working.

I can understand that you might want to have a list of a half a dozen or so useful setting, but not every setting in the file.

[steeb]

To be honest, I dont think you should try to document config.xml. It was never intended to be something was user editable. I change it every release. I'm always adding new settings. Sometimes I'm repurposing old settings. Some of the settings are experimental, and not necessarily working.

I can understand that you might want to have a list of a half a dozen or so useful setting, but not every setting in the file.

sub, I have to, politely, dis-agree

I think this is EXACTLY the sort of thing that needs documentation for advanced users. The fact is it is user editable. If people open the config.xml they will naturally wonder what things do.

Experimental can be flagged as such.

This is why I also asked some many months back with any new release notes if any config.xml changes could be bundled together for easier spotting from documenter's.

Totally understand your views on this, but..... (I also know that this has now opened a discussion that could go on forever :eek: )

cheers

steeb

[sub]

Ok, we'll just have to agree to disagree on this one.

[imilne]

Ok, we'll just have to agree to disagree on this one.

I guess we will :p

I'll keep going where I can - because I believe it's important to have this stuff documented - and if we turns out we can't decode some of the settings, then it sounds like they're more likely to be the ones we shouldn't be messing with anyway.

Iain