Re: [hugin-ptx] -v argument for cpfind in assistant files : mistake or missing documentation?

2024-03-21 Thread 'T. Modes' via hugin and other free panoramic software
chamele...@protonmail.com schrieb am Donnerstag, 14. März 2024 um 01:41:13 UTC+1: Ok, so it's only documented in --help but not in man cpfind. To me the manual is usually supposed to be more complete than the help, so I use "man command" most often. Currently there are 3 possible places: * p

Re: [hugin-ptx] -v argument for cpfind in assistant files : mistake or missing documentation?

2024-03-13 Thread 'ChameleonScales' via hugin and other free panoramic software
Ok, so it's only documented in --help but not in man cpfind. To me the manual is usually supposed to be more complete than the help, so I use "man command" most often. Thanks for the anwser. -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You

Re: [hugin-ptx] -v argument for cpfind in assistant files : mistake or missing documentation?

2024-03-12 Thread wirz
Hello chameleonscales@protonmail, cpfind -h tells me that '-v' stands for 'verbose', so it is completely expected that only the amount of printed output and not the result will be affected. cheers, lukas On 12/03/2024 23:45, 'ChameleonScales' via hugin and other free panoramic software wro

[hugin-ptx] -v argument for cpfind in assistant files : mistake or missing documentation?

2024-03-12 Thread 'ChameleonScales' via hugin and other free panoramic software
If you open a native user-defined assistant file such as normal.assistant (under /usr/share/hugin/data/assistant/ on Linux), there is a -v argument in the cpfind command. I compared resulting files with and without this argument and apart from cpfind's non-deterministic control point generation