hugin-devs team mailing list archive

[Impi <684702@xxxxxxxxxxxxxxxxxx>]

I have solved the problem by adding a new bool variable in the MainFrame 
class. This variable is required to determine whether the confirmation 
dialog was closed with the Cancel button. The patch is attached.

** Patch added: "changes.patch"
   https://bugs.launchpad.net/hugin/+bug/684702/+attachment/2088604/+files/changes.patch

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

Title:
  unsaved changes lost when cancelling save

Status in Hugin - Panorama Tools GUI:
  Confirmed

Bug description:
  When you hit "quit" when there are unsaved changes, you get a warning
  popup.

  So you hit "save".

  When it asks for the filename, you think: Wait, let's try XYZ. so
  instead of saving you want to go back. So you hit "cancel".

  Hugin now exists without saving. Ooops.

  The warning popup also has a cancel. That will cancel the quit and not
  lose your data. That the "cancel" in the "enter filename" would cancel
  the save and quit instantly surprised me.

  I agree, that in a sense this makes sense, but I can easily imagine
  that others would be surprised by this too.