RE: [Inkscape-user] Kernel Panic - Recovery File would be useful
Thanks for the info, Ted.
As regards the autosave feature, I'm thinking in terms of a periodic backup to file during normal operation (not prompted by a crash).
Be interesting to get users' views if there are major disadvantages, though I can see any. Should this be an option? Active by default?
The dialog on restart would be complementary to this background save behaviour, telling you that there was an image available to be recovered.
I'll write up a feature request when I'm back at a networked desktop.
Cefn http://cefn.com BT Labs http://labs.bt.com
-----Original Message----- From: inkscape-user-admin@lists.sourceforge.net [mailto:inkscape-user-admin@lists.sourceforge.net] On Behalf Of Ted Gould Sent: 06 October 2005 17:17 To: inkscape-user@lists.sourceforge.net Subject: Re: [Inkscape-user] Kernel Panic - Recovery File would be useful
cefn.hoile@...1039... wrote:
Is it stored as a matter of routine, or only when Inkscape knows it's going down? What is the naming convention?
Inkscape only saves them when it knows that it is going down, something like a segmentation fault. If the whole OS crashes, I don't think there
is anything Inkscape can do. (I would imagine that a kernel panic would
limit writes to the disk even if Inkscape knew that it was going on).
As far as a dialog on startup, I think that's a good idea. If you could
submit an enhancement request for it, that would be great!
http://sourceforge.net/tracker/?group_id=93438&atid=604309
--Ted
------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Inkscape-user mailing list Inkscape-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-user
cefn.hoile@...1039... wrote:
Be interesting to get users' views if there are major disadvantages, though I can see any. Should this be an option? Active by default?
It should happen in a background thread which gets triggered by a timer.
Just a short story to illustrate my point: CorelDraw has autosave which was enabled (every five minutes).
CorelDraw took four minutes to load the image.
It took nine minutes to draw it (complex image, slow PC, old version of CorelDraw).
And seven to autosave.
Presto: Endless loop.
So do it in the background and make sure it doesn't disturb the user or, even better, save the undo-buffer in a kind of log file. This way, you can have a video of the drawing how it was done (redraw while you load the file), too and saving the changes takes almost no time, especially when you choose a format where you can simply append to the existing file.
Aaron Digulla <digulla@...310...> wrote:
cefn.hoile@...1039... wrote:
Be interesting to get users' views if there are major disadvantages, though I can see any. Should this be an option? Active by default?
It should happen in a background thread which gets triggered by a timer.
Just a short story to illustrate my point: CorelDraw has autosave which was enabled (every five minutes).
CorelDraw took four minutes to load the image.
It took nine minutes to draw it (complex image, slow PC, old version of CorelDraw).
And seven to autosave.
Presto: Endless loop.
So do it in the background and make sure it doesn't disturb the user or, even better, save the undo-buffer in a kind of log file. This way, you can have a video of the drawing how it was done (redraw while you load the file), too and saving the changes takes almost no time, especially when you choose a format where you can simply append to the existing file.
It sould also be possible for the user to disable the feature, for exactly the reasons above!
Bungee wrote:
It should happen in a background thread which gets triggered by a timer.
Just a short story to illustrate my point: CorelDraw has autosave which was enabled (every five minutes).
CorelDraw took four minutes to load the image.
It took nine minutes to draw it (complex image, slow PC, old version of CorelDraw).
And seven to autosave.
Presto: Endless loop.
So do it in the background and make sure it doesn't disturb the user or, even better, save the undo-buffer in a kind of log file. This way, you can have a video of the drawing how it was done (redraw while you load the file), too and saving the changes takes almost no time, especially when you choose a format where you can simply append to the existing file.
It sould also be possible for the user to disable the feature, for exactly the reasons above!
Well, it should not be possible to get an endless loop like that no matter how you set the values. The best solution would be a background thread which gets triggered, makes a copy of the current drawing, saves it and then listenes for the next event (dropping all those which happened in the meantime).
Of course, the save-the-undo solution would be better (I think that's what Vim does) but that depends on the structure of objects on the undo stack. If the structure is very simple, it might be possible to write a generator which creates the object savers from the source so you would get a couple of cool possibilities almost for free.
Just a short story to illustrate my point: CorelDraw has autosave which was enabled (every five minutes).
CorelDraw took four minutes to load the image.
It took nine minutes to draw it (complex image, slow PC, old version of CorelDraw).
And seven to autosave.
Presto: Endless loop.
Yeah, but it shouldn't have auto-saved it if there was no changes.
-kt
(crud below) --
Please consider our environment before printing this email.
WARNING - This email and any attachments may be confidential. If received in error, please delete and inform us by return email. Because emails and attachments may be interfered with, may contain computer viruses or other defects and may not be successfully replicated on other systems, you must be cautious. Westpac cannot guarantee that what you receive is what we sent. If you have any doubts about the authenticity of an email by Westpac, please contact us immediately.
It is also important to check for viruses and defects before opening or using attachments. Westpac's liability is limited to resupplying any affected attachments.
This email and its attachments are not intended to constitute any form of financial advice or recommendation of, or an offer to buy or offer to sell, any security or other financial product. We recommend that you seek your own independent legal or financial advice before proceeding with any investment decision.
Westpac Institutional Bank is a division of Westpac Banking Corporation, a company registered in New South Wales in Australia under the Corporations Act 2001 (Cth). Westpac is authorised and regulated in the United Kingdom by the Financial Services Authority and is registered at Cardiff in the United Kingdom as Branch No. BR 106. Westpac operates in the United States of America as a federally chartered branch, regulated by the Office of the Comptroller of the Currency.
Westpac Banking Corporation ABN 33 007 457 141.
participants (4)
-
unknown@example.com
-
Aaron Digulla
-
Bungee
-
Kinsley Turner