On Tue, Dec 07, 2010 at 12:47:47AM -0000, Yuv wrote:
> Share the patch please. Can't promise (lot of things on my todo list),
> but if it still does not have a preference setting I can contribute
> that.
>
> Place = storage space in the file system? how about taking the time when
> the Hugin instance is started, make it into an epoch, and save it to
> something like /etc/${epoch}.pto ?
/etc is out of the question.
$HOME/.hugin-autosave.$$.pto
($$ = the PID of the running process)
would work fine for me. The question is: who cleans this up?
How about:
$HOME/.hugin-autosave.nn.pto
where nn is a number from 1 to ten. This way you have 10 backups of at
most ten running hugin processes. You don't have to delete them if you
quit. (Sometimes having a backup from a previous session is useful!)
Thus at startup, you'd
rename $HOME/.hugin-autosave.9.pto $HOME/.hugin-autosave.10.pto
rename $HOME/.hugin-autosave.8.pto $HOME/.hugin-autosave.9.pto
rename $HOME/.hugin-autosave.7.pto $HOME/.hugin-autosave.8.pto
rename $HOME/.hugin-autosave.6.pto $HOME/.hugin-autosave.7.pto
rename $HOME/.hugin-autosave.5.pto $HOME/.hugin-autosave.6.pto
etc.
and then start saving in
$HOME/.hugin-autosave.1.pto
but we'd need to keep the filedescriptor to this file so that we'd
keep on saving to the right file even as our autosave file is moved to
a new name by a new instance....
Rogier.
--
** <email address hidden> ** http://www.BitWizard.nl/ ** +31-15-2600998 **
** Delftechpark 26 2628 XH Delft, The Netherlands. KVK: 27239233 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement.
Does it sit on the couch all day? Is it unemployed? Please be specific!
Define 'it' and what it isn't doing. --------- Adapted from lxrbot FAQ
On Tue, Dec 07, 2010 at 12:47:47AM -0000, Yuv wrote:
> Share the patch please. Can't promise (lot of things on my todo list),
> but if it still does not have a preference setting I can contribute
> that.
>
> Place = storage space in the file system? how about taking the time when
> the Hugin instance is started, make it into an epoch, and save it to
> something like /etc/${epoch}.pto ?
/etc is out of the question.
$HOME/. hugin-autosave. $$.pto
($$ = the PID of the running process)
would work fine for me. The question is: who cleans this up?
How about:
$HOME/. hugin-autosave. nn.pto
where nn is a number from 1 to ten. This way you have 10 backups of at
most ten running hugin processes. You don't have to delete them if you
quit. (Sometimes having a backup from a previous session is useful!)
Thus at startup, you'd hugin-autosave. 9.pto $HOME/. hugin-autosave. 10.pto hugin-autosave. 8.pto $HOME/. hugin-autosave. 9.pto hugin-autosave. 7.pto $HOME/. hugin-autosave. 8.pto hugin-autosave. 6.pto $HOME/. hugin-autosave. 7.pto hugin-autosave. 5.pto $HOME/. hugin-autosave. 6.pto
rename $HOME/.
rename $HOME/.
rename $HOME/.
rename $HOME/.
rename $HOME/.
etc.
and then start saving in
$HOME/ .hugin- autosave. 1.pto
but we'd need to keep the filedescriptor to this file so that we'd
keep on saving to the right file even as our autosave file is moved to
a new name by a new instance....
Rogier.
-- www.BitWizard. nl/ ** +31-15-2600998 **
** <email address hidden> ** http://
** Delftechpark 26 2628 XH Delft, The Netherlands. KVK: 27239233 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement.
Does it sit on the couch all day? Is it unemployed? Please be specific!
Define 'it' and what it isn't doing. --------- Adapted from lxrbot FAQ