Comment 2 for bug 684826

Tomas, Currently the progress reporting is already much better than before: previously autopano-sift would update the gui continuously and the text output only every now and then. This resulted in lots of CPU time wasted for updating the screen, which could have better been used in working on finding my control points.

So, yes, it's quite reasonable, and works fine today. So it's a wishlist item.

The thing is, if my computer becomes 10 times faster, it will be updating the screen faster than I can see. That's useless. And even if it is only spending 5% of the time updating the screen, it could become 5% faster on a large pano a few years from now. That's why I suggest to use a time-based update frequency and not a "work progress".

If we turn it around. Suppose I were to run this on a 100 times slower computer (a 486). It would update at most only twice a minute. This leaves the user in the dark about the progress much too long. So the current "every 250 checks" works reasonable on reasonably modern hardware. But we can't say anything about the hardware from 10 years ago, or 10 years from now. I would prefer to change the software now to be future proof.