Request: Autosave every ... minutes

Replies to This Discussion

Permalink Reply by Danny Boyes on November 27, 2013 at 7:30am

+1

EDIT: I would even go so far as to say X Minutes after a change, so that you don't get needless autosaves in the background when you are using other software

Permalink Reply by David Rutten on November 27, 2013 at 7:52am

Autosaves are triggered by changes to a document, so there should never be needless saves. What I can do is put a minimum time between autosave events, so that you never get two autosaves within the same X seconds/minutes. Would that be an ok solution?

--

David Rutten

david@mcneel.com

Permalink Reply by Danny Boyes on November 27, 2013 at 7:59am

I meant if it was only time based. I think a minimum time setting after an event would be a good addition

Permalink Reply by David Rutten on November 27, 2013 at 8:28am

And then when another event happens in that timeframe? Does the save get delayed? What if you keep adding components and wires furiously for 4 hours and all autosave events are delayed, then you crash? Sounds bad.

To take a step back, the main problem here seems to be that it takes a long time to save a file. I wonder how much time can be gained here by putting stuff on background threads or caching and reusing data.

Basically I need to find out where all the time is spent during a save (is it creating the chunks for all the components? Is it converting internal Breps and Curves to byte-arrays? Is it maintaining the GH file database? Is it compressing the byte-array? Is it writing the bytes to the disk? etc. etc.) and then see if it can be sped up. If we can bring the time down it takes to save a file from 5 seconds to 5 milliseconds, the whole problem goes away right? No need for finicky settings.

--

David Rutten

david@mcneel.com

Permalink Reply by phillip on November 27, 2013 at 9:02am

Seems like , I didn´t see your comment when I wrote my response.

You are absolutely right and I like your attitude.

Please, also consider the other autosave-without-filename request mentioned below.

Thanks.

Permalink Reply by Danny Boyes on November 27, 2013 at 9:17am

The scenario I was trying to describe was that it only auto saved after a minute (for example) regardless of what you did in the mean time. But it wouldn't continue to save every minute if nothing was happening in the Grasshopper UI. Timers should be exempt so that the result of a timer being left to run does not trigger the auto save process

Permalink Reply by phillip on November 27, 2013 at 8:38am

Not sure.

It would be good to have an time base option, whenever I turn all the event based options off.

-I know, I should not do this-

For sure it makes more sense to make them event based in terms of creating them at a meaningful stage. Still though, it can really be a pain if they always happen, when you want to do something - especially with big files.

So the idea was, if they are time based, there is the chance it also hits a moment, when I am thinking about my next step or just checking my email.

May be the minimum time would be a solution - or maybe also just a delay.

And please also let GH create an autosave whenever you start working on a file, even without saving it at all.