hugin-devs team mailing list archive

[Yuv <679917@xxxxxxxxxxxxxxxxxx>]

use hg export to produce the patch.  hg help export is your friend.

for example, if the code was committed in one go, then hg export -g
${REV} > feature.patch will produce a patch.  If it was committed in
multiple steps, then hg export -g ${STARTREV}:${ENDREV} > feature.patch
will do the trick. You will need to identify the revision number at
which you did commit.  hg view is your friend there. you will need to
activate the hgk extension in your ~/.hgrc settings.

There is a place in the code where a random temporary file is generated
for stitching.  I don't recall anymore where it is.  You could orient
yourself to that for both place and filename - AFAIK it works well on
all systems.

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

Title:
  Backup copy of project.

Status in Hugin - Panorama Tools GUI:
  Confirmed

Bug description:
  Hugin just crashed on me. Pre 0.7.0 this happened so often that I knew I had to save often, or risk losing my work. 

So far this is the first since I went to 0.7.0. Now 0.8.0 crashed on me.... However I'm most pissed that a pto file got saved to run "nona", but this gets (I think) cleaned up after running nona. So now I'm left with a project file with hours of work missing. 

PLEASE write a backup pto file where I can find it, or mention "this project had unsaved changes when hugin crashed, load the backup file?" when I start it. (then I don't need to know where the backup is stored...).