hugin-devs team mailing list archive

[Jason Sims <687301@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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.

** Affects: hugin
     Importance: Undecided
         Status: New

-- 
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:
  New

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.