> Just removing it from the installer doesn't mean the user can't use it > in the future. It's just a matter of creating a new CPG entry and > populating it with the desired calls. I agree that stacks are a good > thing, that's why I tried to find a way of keeping the entry by > replacing the two-step CPG process involving autopano/generatekeys by > something the user might have already (he may or may not have any of > the CPGs, since the user can choose which to install).
You can use the multi-row detector also with other cp detectors (like panomatic, select then one-step detector). But using the two-step approach (involving autopano/generatekeys from autopano-sift-c) has advantages. In this case each image is only probed once to find keypoints. The keypoints are cached to disc. At the end the temp files are deleted. If you call inside a script, you break this functionality. Thomas -- You received this message because you are subscribed to the Google Groups "Hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx
