Comment 4 for bug 679917

Revision history for this message
rew (r-e-wolff) wrote :

Dear Thomas,

I was working on a project. Instead of putting my images around the circle hugin placed all images at 0,0,0. That is not how I shot things. So I went to the "preview" window, and tried dragging the images, so that they wouldn't be on top of eachother. That's when HUGIN ITSELF CRASHED.
IT TOOK ALL MANUAL CONTROLPOINT EDITS WITH IT. NO SAVING POSSIBLE. PROCESS GONE. DATA GONE.

Your assumption that it happened when stitching or that no dataloss happened is WRONG.

This IS a real data-loss problem. I'm FINE with the developers not getting around it before christmas. But PLEASE do not put this as "wishlist" again. It is a significant problem.

This, saving the intermediate hugin file every now and then, is a surefire way of diminishing the consequences of an unexpected crash. If we take this seriously, a day of grudgework will reduce the severity of an unexpected crash to "bad luck, just restore from the autosave". Otherwise all crashes HAVE to be considered a showstopper.