|
 |
"JYR" <jyr### [at] hotmail com> wrote:
> Dear Aek,
>
> Since you cannot set image dimension from within the scene description, but,
> you have access to image_width and image_height, you can work around this
> the other way.
>
> *Have POV-Ray make the computations, including Requested_image_width and
> Requested_image_height.
> *Then have them compared against the built-in variables image_width and
> image_height in a #if or a #switch statement
> *If they match, POV-Ray keeps on rendering.
> *If not, have POV-Ray create an INI file with proper width and height (see
> documentation section 3.2.2.3 for opening and writing to a file) and abort
> without rendering.
>
> It still is cumbersome, as it is a 2 pass process. But at least the same
> scene file is used to perform the computations in both case, which is much
> less error prone.
>
> Hoping this helps !
>
> JYR
Dear JYR,
Sorry for this late reply and thank you for your suggestion. It looks quite
attractive since the code could be stored in one place. I'll see if I can
create some queing system on top of the file system so this process can be
continued in a loop until no more INI files are left.
Aek.
Post a reply to this message
|
|
