I set up the directory for auto save when I installed 0.47. I've never seen a file appear in that directory.

Now Inkscape has crashed. First time in a while that I've lost an hour of work since 0.47. It said it saved a file (in the crash message), but I've looked and it didn't. And there are no auto save backups.

Does this work for anyone? I'm on WinXP.

f.

Thanks... I've searched my entire disk and haven't seen any auto save files that I can identify.

Still wondering if it works. Just had another crash. Unhandled exception at 0059EB7C. WinXP.

I'd just finished editing a gradient definition, and was about to move 2 nodes via the Tool Control. Not sure if I'd typed the new Y location yet or not.

Kjohrf wrote:I'd just finished editing a gradient definition, and was about to move 2 nodes via the Tool Control.

Was the object with the gradient the parent of any clones in your drawing?
(you know what follows: could be #453067)

Kjohrf wrote:Still wondering if it works.

The path that you entered in the Inkscape Preferences dialog as 'autosave' location does exist? Inkscape cannot create the folder itself AFAIK.

I know this could well be a platform specific issue (win32). Anyway - I never used autosave before, but just set it up for a test with interval 5min and the path to a newly created directory for my autosave files (entering the full path name in unix syntax: '/Users/my_name/tmp/autosave') and opened & edited an existing drawing:

• after 5 minutes a new file appeared in the designated folder:
  ('inkscape-autosave-503-2009_12_07_23_17_12-001.svg')
• then I reproduced a crash when editing a radial gradient as described in the linked bug report and Inkscape created an emergency-save file ('tangram-exclusion-.2009_12_07_23_19_02.0.svg') in my $HOME folder.

So on OS X this experiment leaves me with both the autosave backup and the emergency save with the latest version right before the crash.

OK - two replies in one!

First, the object I was changing was not a clone. I did have two almost identical objects, but I'd duplicated, not cloned. I was using the pop-up gradient editor, not the on-image handles and such.

Ah - looks like I had a typo in the backup directory name. Didn't catch it the first couple times checking. A browse button there would help. Let's see if it works now. Tap, tap, tap... <whistling Dixie> Re-starting Inkscape. Making modification. More tapping and whistling. Woot. There it is. I see a back-up. Thanks!

Kjohrf wrote:Ah - looks like I had a typo in the backup directory name. Didn't catch it the first couple times checking. A browse button there would help.

This could get part of the filed RFE #490338 “Try to create the autosave directory if that does not exists” ;-)

Geesh. Just when I said 0.47 doesn't crash, now it's 2 in 2 days. This time, I'd selected 2 of 6 nodes, and used the up- and down- scrolls in the Tool Control to change the Y location. Crash. At least with 5-minute auto save, it didn't cost me too much.

Crash not reproduced when node-editing a 6-node-path and - with two nodes selected - using the scroll arrows of the Y-coordinate entry field. Once they have moved to the initially average y-coordinate of all selected nodes, further changes with the scroll arrows just continually moves all selected nodes following the changed y-coordinates (up or down). Does you path have a pattern fill?

Edit: nope, a pattern fill doesn't crash when moving only few selected nodes (does however have the tendency to crash when selecting all nodes - including the pattern handles - and move the object still in node-editing mode)

I have two such paths - the same size, one on top of the other. The top is not 100% opaque, and has a pattern. The bottom is 100% opaque, and just has a fill color.

I just reproduced the crash by change a node on the top one (see above). I think I just had one node selected this time, and typed the new Y value. Tried it again, and it didn't crash. Go figure.

Unfortunately node-editing pattern-filled paths seems to be "crash-prone" in Inkscape 0.47 (see also this recent question asked in inkscape-devel)

~suv wrote:Unfortunately node-editing pattern-filled paths seems to be "crash-prone" in Inkscape 0.47 (see also this recent question asked in inkscape-devel)

Thanks. Glad to see someone is trying to find someone to work on it.