icpfind is only a wrapper around the different control points detectors. It "simply" calls the detectors and waits for the results. It does not have access to the internal of the different control points detectors.
If the wish is for cpfind, I think cpfind reports enough progress. Also the matching phase is significant faster than the loading/remapping/detection phase; so I see no point in adding more progress indicators for matching. -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/684826 Title: icpfind reports progress every 250 cross matches. Status in Hugin - Panorama Tools GUI: Triaged Bug description: This is just fine for my current projects. For small projects it might update slightly too fast (too much useless overhead in painting the screen) while for a large project it goes a bit slowly. This means that it depends on the size of the project how fast the updates come. But most of all the updates depend on how fast my CPU is. To make the software future proof, we should make it for example: - set a timer to go off twice a second. - in the timer set a flag. - in the mainloop (e.g. every 1, 10 or 50 matches) check for the flag and print the progress if set. Reset flag. (this is the most sure-fire way to prevent IO concurrency problems. ). _______________________________________________ Mailing list: https://launchpad.net/~hugin-bug-hunters Post to : [email protected] Unsubscribe : https://launchpad.net/~hugin-bug-hunters More help : https://help.launchpad.net/ListHelp
