[Hugin-devs] [Bug 685224] Re: save / load CP generator settings doesn't work
[Expired for Hugin because there has been no activity for 60 days.] ** Changed in: hugin Status: Incomplete = Expired -- 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: Expired 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)? ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 685224] Re: save / load CP generator settings doesn't work
** Changed in: hugin Status: Triaged = Incomplete -- 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: Incomplete 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)? ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 685224] Re: save / load CP generator settings doesn't work
- Export saves all cp detector settings, not only the selected one (therefore point 1 and 4 are invalid) - The missing extension is fixed in repository. - I can not reproduce the empty setting file (on windows it is correctly saved). I added a Flush to explicitly save it. This hopefully fixes the issue, but I can not test. ** Changed in: hugin Status: New = Triaged -- 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: Triaged 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)? ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
