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#151 - No way to cancel save while parsing, never ending errors

Attached to Project: POV-Ray
Opened by Mike H (SharkD) - Friday, 25 June 2010, 20:01 GMT
Last edited by William F Pokorny (wfpokorny) - Saturday, 21 January 2017, 16:06 GMT
Task Type Possible Bug
Category Platform-specific → Runtime error
Status Tracked on GitHub
Assigned To No-one
Operating System Windows 7
Severity Low
Priority Normal
Reported Version 3.70 beta 37a
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

On Windows, when I try and save a file while it is being parsed prior to rendering, I get an error, “Failed to save file: The operation completed successfully”, with a single OK button to click. Despite the weird wording, I’m OK with that.

However after clicking OK I get the error, “Failed to save file ‘...’“, with three buttons: Cancel, Try Again, Continue. Not sure what “Continue” means in this context, given that the possibilities would seem to be covered by the other two buttons. Whatever.

Also, sometimes I get a message with only a single “Retry” button. Not sure what the exact message was.

Anyway, the real problem is that, regardless of which button I press, the program continues to spawning the same error message endlessly. Luckily there is a delay between them, but still it would be nice to have at least one of the three buttons *stop* POV-Ray from asking me again.

Also, once the program finishes parsing the file and it becomes possible once again to save the file, it does nothing. I.e. it doesn’t save the file. So what’s the point of the message and all the options? Why not just say, “Unable to save the file, file is parsing” and be done with it?

I think I recall the same behavior in 3.6.2, so it’s nothing new that’s been introduced.

This task depends upon

Comment by Thorsten Fröhlich (thorsten) - Tuesday, 23 August 2011, 05:52 GMT

Has this changed by now?

Comment by William F Pokorny (wfpokorny) - Saturday, 21 January 2017, 16:06 GMT
  • Field changed: Status (Unconfirmed → Tracked on GitHub)

Now tracked on github as issue #204.

Loading...