hugin-devs team mailing list archive

[Yuv <687301@xxxxxxxxxxxxxxxxxx>]

Hi Thomas,

thanks for the info.  I simply copy & pasted from the Hugin FAQ.  I am
not sure if it is up to date, and I anyway believe that with the new
Makefilelib things have improved.

That said, I don't think in the reported case it has to do with
Makefilelib since it is the CP detection that fails.  So maybe it is the
CP detector used that can't digest the special character?

There are too many parts (including third party tools) involved in this
kind of issue and considering platofrm-specificities makes it even more
complex.  I would be inclined to stick with the minimum common
denominator, i.e. if a character is invalid in the filename of a single
tool and on a single platform, declare it invalid throughout the
application and prevent use of it in a gracious way wherever possible,
i.e. mentioning that the files are not being accepted because one of the
blacklisted characters is used in the filename.

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/687301

Title:
  Single quote in path of loaded image causes control point detection to fail

Status in Hugin - Panorama Tools GUI:
  Invalid

Bug description:
  Just ran into a weird issue with Hugin 2010.2. If you load images that have a single quote anywhere in their path, control point detection will always fail, no matter which detector or what settings. Something is not being escaped properly.

E.g., if you're loading images stored in:
/Users/you/Desktop/Friend's Birthday/…

When you click (Align), you'll get errors in the little console window that pops up while control point detection is happening. Unhelpfully, this window appears and disappears so quickly, you can't even read the details. It would be nice if those errors could be written to a log file or something. Very frustrating having the console window immediately vanish when you're trying to see WHAT the damn problem is.

For now the workaround is to just make sure you don't have any single quotes in the path of any images you're loading.