Le 17/12/2013 15:36, clipka a écrit :
> Am 17.12.2013 13:36, schrieb David Given:
>> On 17/12/13 08:35, clipka wrote:
>> [...]
>>> A quick glance at the code indicates that someone had already thought of
>>> this, and all the necessary stuff seems to be there already, except that
>>> it hasn't been hooked up to a command line option or ini file setting
>>> yet. Two lines of code should get us going.
>>
>> Is there a way to specify the location? There's value in having the
>> pov-state file written to a different directory to the output file ---
>> for example, a local drive rather than a network drive in the OP's case.
>> It would then be trivial to extend to 'write nowhere'.
> 
> As I said, the "write nowhere" feature is already there behind the
> curtains, it's just not exposed via a command line switch yet.
> Implementing a way to write to a different directory would need more
> effort.
> 

about the entry: what about
+AC / -AC : Allow_Continue = true/false ?

(because I prefer to see it as a functionality rather than a technical
details: should the pov.state file mechanism be changed for something
else, the +C would still be the command to use to continue an aborted
render)

Looking at available options, B is parameterless, BM & BS exist.
C is parameterless and alone, so BT , CT and other are possible.

From the option name: BT (BackupTrace) seems natural.
Yet, I would prefer AC (and it is possible too).


-- 
Just because nobody complains does not mean all parachutes are perfect.

Post a reply to this message