hugin-devs team mailing list archive
-
hugin-devs team
-
Mailing list archive
-
Message #01950
[Bug 786204] Re: cpfind --kall -o does not output PTO file
Sorry, but your patch introduces an user unfriendly behaviour: When
starting without -o switch it runs the whole cp finding and matching
(which can be time consuming) and at the end *no* output is written.
Also when starting with e.g. "-k 0 -k 1" instead of -kall this will not
produce the wanted behaviour (it will only find the matches between
image 0 and 1 and ignore all other image pairs, or in the worst case it
will crash), please have a better look into the code before starting
hacking.
Also then "k+o" would not be "cache". The k switch forces the keyfiles
to be regenerated even if they exists. This does not happen with cache
switch. So there is a right to live for both, even if you personally
does not need one of them.
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/786204
Title:
cpfind --kall -o does not output PTO file
Status in Hugin - Panorama Tools GUI:
Confirmed
Bug description:
when entering the command cpfind --kall -o out.pto in.pto I would expect
a) all .key files for the input images to be stored on disk
b) out.pto to be equally stored on disk
indeed the first part happens, but the second not and I must repeat
the command cpfind -o out.pto in.pto to obtain the expected result
Follow ups
References