Not Saving

Is anyone else having problems saving documents. I hit the save button and the message lower left of the canvas indicates I did save. However, when I go to look at the most current version, it does not reflect the recent save. The only way I can get a new document to save is to Save As to a new name. Otherwise, GH will not save the current file even though the message in the bottom left says it did.

Is this something with my machine or with GH.

I also notice at times when I hover the mouse over the output of a component, I do not get the pop up showing what is being output. This problem is sporadic. It operates normally when I first open a definition, but after some time I don't get the pop up.

Is it me or something else.

Thanks for any assistance.

Stan

Replies to This Discussion

Permalink Reply by David Rutten on July 20, 2011 at 2:50pm

Hi Stan,

very peculiar. I've rechecked the file saving code, and it should only claim the save was successful if the file has indeed been saved. When a file is saved and it already exists on the disk, then I first save the file to a temp folder. Only when that file write is successful, do I replace the old file with the new file. If you SaveAs, then the file is written to the proper location immediately.

Can you check if the Modified Date of the file in Windows explorer changes when you do one of these failing saves?

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by Stan Carroll on July 20, 2011 at 5:20pm

David,

The modified date remains the same no matter how many times I save. I noticed it is doing the same thing in rhino as well as in GH. Thanks for taking a look at this.

Stan

Permalink Reply by David Rutten on July 21, 2011 at 3:09am

Are you saving to a local disk or a network drive? Are you sure you have rights to that location. I can basically see two possible scenarios that would explain these facts:

Windows is lying about a file write/file move operation. It tells me (i.e. the Grasshopper code) it did as requested, but in the meantime fails to actually overwrite/delete/move the file. This seems unlikely, as Windows is typically pretty good at bitching when it's instructed to do something that goes against security protocol.
Something is re-instating old files after a change. It could be a virus doing something naughty, it could be a virus-scanner getting confused, it could be some other security layer undoing what it perceives as damage.

My first instinct would be to say there's a bug in Grasshopper*, but since the same problem also happens with Rhino this seems less likely. Have you tried saving *.txt files with NotePad to the exact same location?

David Rutten

david@mcneel.com

Poprad, Slovakia

*Andy's first rule of programming: it's always your own damn fault.

RSS