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.
Attached to Project: POV-Ray
Opened by Christoph Lipka - 2009-05-18
Last edited by Thorsten Fröhlich - 2010-06-20
Opened by Christoph Lipka - 2009-05-18
Last edited by Thorsten Fröhlich - 2010-06-20
FS#30 - Custom progress information during parsing
For some particularly “heavy” SDL scripts, it might be desirable to override (or complement) the standard “Parsing 47110815K tokens” progress information with some more helpful custom info, e.g. “Planting trees... (37%)”, or “Generating terrain mesh row 47 of 500”.
Closed by Thorsten Fröhlich
Sunday, 20 June 2010, 06:30 GMT
Reason for closing: Duplicate report
Additional comments about closing:
Sunday, 20 June 2010, 06:30 GMT
Reason for closing: Duplicate report
Additional comments about closing:
Actually, I just noticed that this more
or less a duplicate to #28.
This is possible with the #debug stream output.
Using #debug for this purpose has its limitations:
- You can't force an output without producing a linefeed.
- On Windows systems, it might be desirable to present the information in the status bar.
Previously POV-Ray supported writing to the status stream, but this has several issues. In particular, it is next to impossible to throttle the rate of messages output by a scene file. Due to the message passing nature of the backend-frontend communication, status messages can easily flood the message queues and severely slow down parsing. For debug output this is less of a problem because the problem is "visible" to the user when seeing tons of debug output lines per second. The status output would hide this effect, and there is no meaningful way to decide which messages to skip.