-v argument for cpfind in assistant files : mistake or missing documentation?

[ChameleonScales]

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 which always brings differences on each run, I didn't find any noticeable difference.

Is that an actual but undocumented argument or was it put there by mistake ?

[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

[ChameleonScales]

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.

[T. Modes]

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:

* program --help

* man program -> only on Linux, but not on Windows

* help pages in the GUI

When I add new switches I always add it to the program --help output. This should be the up to date place.

The other 2 places may be out of date.

In case of the help pages you can help and edit these pages on the wiki.panotools.org. They will then be update before a new release.

For the man pages, which are only available on Linux, updates from users are welcome. If you send a patch file with your proposed changes they can be easily incorporated.

Thomas