[Hugin-devs] [Bug 786204] Re: cpfind --kall -o does not output PTO file

2011-05-22 Thread Yuv
Attached is a patch that fixes this feature behavior that IMHO is unintuitive, convoluted, user-unfriendly. why do we need three switches then (k, cache, o), when just two are enough to achieve the same with less strain on user's memory? why do we need to override the user's instruction when the

Re: [Hugin-devs] [Bug 786204] Re: cpfind --kall -o does not output PTO file

2011-05-22 Thread Yuv
On May 22, 2011 11:40:09 AM tmodes wrote: 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. how is this different from starting with