On 4/14/25 07:47, jr wrote:
>> With a lot of test images and reuse of scenes I loose track of command line
>> settings, camera settinges etc.
> had me thinking that, at least for the *NIX builds, one could have POV-Ray dump
> its argv[] to a '~/.povray_history', to help with that.  (WFP ? :-))

Hi jr.

Phase of the moon maybe - or that many of us have tax time hangovers...

It happens, I'm about a week into another run at replacing the POV-Ray 
(yuqk), command line and ini parsing(*). I've patched bugs in the yuqk 
fork over time, but many remain.

The one probably most important for the metadata subject is that our 
current, to ini file, dump mechanism isn't covering all the options - no 
matter how options are set. Also, the thread count setting, for example, 
should probably not be captured, but always is.

The yuqk fork - given it's rapidly changing - should capture the 
particular release version too. I'm also pushing on ideas like creating 
persistent (perhaps never freed) stuff during the command line / ini 
parsing stage(**). I've not thought about how features like that might 
work with captured rendering states.

As to your particular '?' jr, Something like a ~/.povray_history is 
possible, but does it offer much over the terminal's command history? 
Such a file would be specific to 'povray' and I suppose more persistent? 
The generic, Linux / Unix history capability I do use heavily - to 
render again with the same flags.

Bill P.

(*) - I've started this effort several times over the past five years or 
so - and I've always bailed. Don't hold your breath.

(**) - Anything from simple value, vector, string storage (extended 
'declare' command capabilities) to a new, optional, first parse pass. 
The entire 'first parse' result would be treated as persistent storage.

Post a reply to this message