Ilya Razmanov <ily### [at] gmailcom> wrote:

> Hm, I've seen "Input_File_Name" in "Command-Line and INI-File Options",
> and I always assumed that all this work only with ini and stuff.

It does not control anything.  It's a defined identifier.

> So, it works within scene as well? Where can I learn more about this
> (beside thin NG, I mean.

Always the WIKI:
https://wiki.povray.org/content/Reference:Strings

It also looks like
the link for input_file_name at
https://wiki.povray.org/content/Reference:Keywords
is supposed to have a reference to this keyword - but doesn't.

> Surely I ask questions here sometimes, but
> still I understand that teaching me POVRay is not the main reason for
> this NG existence)?

No way.  Our time machine was invented just to go back and make it all for you!
:)
We all are learners being taught, and become teachers of our own little areas of
experience and expertise.

> There are ways to control stuff from the scene that
> are normally controlled from ini?

.. . . sort of.
If you look at the way the sample scenes get automagically generated from a
script, the script is actually doing the controlling, but it uses the image
sizes that it reads from within the scene file.

Also, if you look up my self-including include file, then you might invent a way
 to parse values in the scene, (over)write to the file, and then include it
again....

You might be able to (re)write the resolution.ini file, or something - but I
think POV-Ray generally doesn't allow for potentially malicious coding exploits.

- BW

Post a reply to this message