hugin-devs team mailing list archive

[zarl <685224@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Applies to Harry's new beta2 of Hugin-2010.4.0 bundle as of 4 Dec 2010.

- clicking "Export" in Prefs -> CP Detectors if no entry is selected
opens a file dialog that assumes that a setting could be exported.
Instead, the Export button should be greyed if no entry is selected

- the 'Export' file dialog doesn't add the necessary '.setting' to a
file name. This extension is needed for the 'import' file dialog to
accept a file. Furthermore it might make sense to automatically use the
description of the actual setting to name the settings file together
with a date/time stamp, e.g. "cpfind-101204-1721.settings"

- Exported settings files are empty, so nothing will be imported yet (I
also opened an exported .setting file with a text editor to make sure
it's really empty).

- What will happen if I import a settings file with the same description
(but different arguments) I already have in my prefs? Do I get the
chance to rename it (favoured) or will it overwrite an existing setting
(bad)?

** 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/685224

Title:
  save / load CP generator settings doesn't work

Status in Hugin - Panorama Tools GUI:
  New

Bug description:
  Applies to Harry's new beta2 of Hugin-2010.4.0 bundle as of 4 Dec 2010.

- clicking "Export" in Prefs -> CP Detectors if no entry is selected opens a file dialog that assumes that a setting could be exported. Instead, the Export button should be greyed if no entry is selected

- the 'Export' file dialog doesn't add the necessary '.setting' to a file name. This extension is needed for the 'import' file dialog to accept a file. Furthermore it might make sense to automatically use the description of the actual setting to name the settings file together with a date/time stamp, e.g. "cpfind-101204-1721.settings"

- Exported settings files are empty, so nothing will be imported yet (I also opened an exported .setting file with a text editor to make sure it's really empty).

- What will happen if I import a settings file with the same description (but different arguments) I already have in my prefs? Do I get the chance to rename it (favoured) or will it overwrite an existing setting (bad)?