Interestingly, it did update the date and time to the exact moment I hit sav even without me closing the file again.
I think then sometimes when a crash happens it does not go back to this time for some reason, but you are right, hitting save did update the date/time in finder.
I think the best bet is CLOSE the file more often to really lock it in.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
The only reason why saving a file would not truly save the file to disk is if the entire operating system crashed between the save operation being called and the disk being actually updated. That’s a vanishingly small window of time, and highly unlikely (at least in my experience over the past couple of years). While I realize that I am bear-baiting fate, I haven’t had any system crashes in years, and I leave my big Mac running 24/7 (mostly to filter my mail while I sleep). I have had application crashes galore, many since upgrading from Snow Leopard to Lion. I haven’t done the Mountain Lion jump, mostly because I don’t feel like re-installing my Ruby environment and development tools. Snow Leopard was the most stable iteration of Mac OS since System 6. (I started with System 4.something, in the late 80s.)
But it is important to understand how data is saved and how an application interacts with the operating system. When you open a document in a modern operating system, the entire document is read from disk into memory (either real or virtual). From that moment on, all operations performed on that document update the version stored in memory. The version on disk remains untouched. An application crash can corrupt the content of the version of a document that is currently open in memory, but it will not alter what is already saved on disk.
When you invoke the save command (regardless how you do that – please don’t imagine that a keyboard shortcut and a menu invocation are in any way different from one another from the running application’s POV), you are sending a message to the operating system: “commit the current state of Document X to disk from memory”. That’s all. You’re making a snapshot of the One True Document (the one open in memory) to the disk.
Freeway adds another layer to this cake: the fwbackup file. This file is updated by Freeway at the moment that a document is opened by the application. It is fully decoupled from the save operation – the only way to update the fwbackup is to close the document completely and re-open it. This is as close as we get to multiple undo at the moment. You open a document, perform some operation on it, and save. Then you make some more changes without saving. If you find yourself really hating the last few things you did (not just the last one, which you can Undo), you can Revert to Saved… and get back to the last point where you saved. But if this entire editing session has been a blind alley, and you want to go back to where you started, you can open the fwbackup file and save it as a new document, and you’ve effectively gotten three levels of undo.
Walter
On Feb 23, 2013, at 8:51 AM, Barry Hoffman wrote:
Interestingly, it did update the date and time to the exact moment I hit sav even without me closing the file again.
I think then sometimes when a crash happens it does not go back to this time for some reason, but you are right, hitting save did update the date/time in finder.
I think the best bet is CLOSE the file more often to really lock it in.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Thanks for all the details Walt. My crashes which only happen about once a month are FW only and not system.
THe thing that still gets me, is that I am almost sure I have hit SAVE numerous times between time “A” and time “B”. But when FW shuts down and I reopen- I am always holding my breathe to see how many things I have to redo; sometimes few days worth, sometimes not much.
From what I got from this thread is that if you hit SAVE, that locks in your FW changes.
If your FW crashes and you have to reopen FW, technically when it opens again all your changes should be there from the last save.
I will have to pay much more attention to how often I hit save then.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Back in the bad old days of System 8 and Mac OS 9, I got into the habit of “Save, then Print” because QuarkXPress was so damned buggy. Command-S-Command-P was a macro in my mind… You might try to encourage yourself to do the same in Freeway.
Walter
On Feb 23, 2013, at 11:31 AM, Barry Hoffman wrote:
Thanks for all the details Walt. My crashes which only happen about once a month are FW only and not system.
THe thing that still gets me, is that I am almost sure I have hit SAVE numerous times between time “A” and time “B”. But when FW shuts down and I reopen- I am always holding my breathe to see how many things I have to redo; sometimes few days worth, sometimes not much.
From what I got from this thread is that if you hit SAVE, that locks in your FW changes.
If your FW crashes and you have to reopen FW, technically when it opens again all your changes should be there from the last save.I will have to pay much more attention to how often I hit save then.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
You might want to install a small utility that takes snapshots of your working document every 5 minutes or so, invisibly and in the background, saving these copies to your chosen ‘cloud’ solution.
See:
He’s written a few different backup type utilities and one of them should work for you.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options