custom tasks - can't specify working directory

[johnsonx42]

Sub, when you get back and have a moment, can you update the Custom Tasks feature so that a working directory can be specified? Some programs expect to find their 'stuff' relative to the current directory, and thus don't work when launched as a custom task.

edit: also, I just discovered that if I disable a custom task, npvr 'forgets' what it is; it's still in the plugin list, but it loses it's parameters and does nothing if re-enabled. I then have to manually fix it or delete it from config.xml. it'd also be nice to be able to edit an existing custom task.

[sub]

I cant do it as a patch, but I've noted it down to add if possible for the next release.

[johnsonx42]

no problem, I've worked around it for the task I was setting up tonight - the app would accept it's config directory as a parameter, and then I hard-coded the absolute paths for everything else into the .ini file.

[imilne]

An easier option might be to just put everything you need into a batch file, and then call that from NPVR. That way you can specify whatever options you want, including getting the correct working directory.

If you're worried about the dos window appearing, then there are plenty of 3rd party tools around that can hide it (http://forums.nextpvr.com/showthread.php...md-windows). In that case, you just add the tool as the custom task, with the batch file you want to run as its parameter.

Iain