POV-Ray

The Persistence of Vision Raytracer (POV-Ray).

This is the legacy Bug Tracking System for the POV-Ray project. Bugs listed here are being migrated to our github issue tracker. Please refer to that for new reports or updates to existing ones on this system.

Tasklist

FS#301 - Fallback to default image size causes wrong values to be printed in message output

Attached to Project: POV-Ray
Opened by Christoph Lipka (clipka) - Friday, 19 July 2013, 08:54 GMT
Last edited by William F Pokorny (wfpokorny) - Sunday, 22 January 2017, 15:30 GMT
Task Type Definite Bug
Category Frontend → Other
Status Tracked on GitHub
Assigned To Christoph Lipka (clipka)
Operating System Windows 7
Severity Low
Priority Normal
Reported Version 3.70 RC7
Due in Version Undecided
Due Date Undecided
Percent Complete 50%
Votes 0
Private No

Details

When resolution is not specified (neither via POVRAY.INI nor via QUICKRES.INI nor via command line or custom .ini file), random values are displayed for image resolution in the Image Output Options message output. (The actual render will be performed at the default size of 160×120 pixels though.)

This task depends upon

Comment by Thorsten Fröhlich (thorsten) - Friday, 19 July 2013, 08:59 GMT

There should be a TryGetInt (assuming this part uses the POVMS C++ interface yet) to get the values when they are displayed. I assume (don't have it at hand) the code currently gets the values in some pre-used variable. Though likely it then would still be based on the POVMS C interface ...

Comment by Christoph Lipka (clipka) - Friday, 19 July 2013, 12:44 GMT
  • Field changed: Status (New → Investigating)
  • Field changed: Percent Complete (0% → 50%)
  • Task assigned to Christoph Lipka (clipka)

I’ve already examined the responsible code: It just blindly assumes that the respective attributes are there. The fix is trivial, but I don’t think it’s important enough to rush it into the 3.7.0 release.

Comment by William F Pokorny (wfpokorny) - Sunday, 22 January 2017, 15:30 GMT
  • Field changed: Status (Investigating → Tracked on GitHub)

Now tracked on github as issue #212.

Loading...