This bug only seems partly fixed.

As I understand the fix currently waits till the user releases the mouse button, preventing any lines being drawn towards the top left corner of the screen whilst drawing.

However if the user is tapping the mouse button while drawing, which is a fairly common procedure. ForeverSave jumps in between button taps and again ends up producing a line drawn from the mouse location to the lop left hand side of the screen.

I like the fix waiting for the mouse button to be released, but it might be better if the mouse could be disabled just before the save function is called. So the user cannot begin to perform a drawing action.

Good luck with the software.

Can you please verify and fix this? (Using FS 1.1.3 on OS X 10.6.2).

Sometimes I do not want to save changes I make to a document. Could you add an option to NOT initially save an opened (but previously saved) document?
For example, let’s say that yesterday I typed and saved a document. Today I open it but don’t want to save any changes. Can I set it up so that it will treat an opened document as if it had not been saved before, and just give me the animated cursor until I do manually save it once?

Thanks, and I love this app. It completes iWork.

Anyway, I’ve been using EverSave for quite some time. I’m really looking forward to test FS ‘Heavy’, but here’s some of the questions I had some hours ago:

1. QuickLook works fine for the file types relevant for me, but how do I spot the differences between versions? Just thinking about ordinary 20 pages (I spotted ‘difference in bytes’ on the first screenshot)
I’m fine with a comparison in the app, but then the direct appeal of a central versioning system is reduced.
I’m aware that file comparison (in real/conventional versioning systems and elsewhere) works best with straightforward text files and the like, and ‘Universal Compare (via QuickLook or else)’ is far out of reach of ordinary human Apple users.

1a. a bug: I just tried to compare three versions of a file. All look the same in QuickLook. Apparently, QuickLook is caught with a single file, rather than three different ones.

2. Where are the backups saved? I couldn’t find that out. I really like to be able to fiddle around with files – unless they’re part of a special format, of course.
Anyway, I want to be sure that Time Machine doesn’t start to backup those backups; on the other hand, I’d like the thought of backing up the FS backups by another backup app… (if you know what I mean)

3. On versions: is it a gradual system or are the files saved as a whole? I could take ‘difference in bytes’ in the early version as a hint. If I use FS with, say, PDFs with graphics, this would matter for my small amount of spare space on my main HD.
(20MB * 50 versions = around1GB and that would be definitely too much…)

4. versioning, part 2:
My favorite scenario is saving every minute or so.
Let’s say I choose 50 versions (assuming my calculation above is wrong).
Do I understand it correctly that the last 50 versions are saved?
That’d be around 50 minutes of backups and that’s far away from a real versioning system (or the imitation via Hazel e.g.). (of course, in combination with Time Machine, that still works out, with one TM backup per hour)

5. On the trial conditions:
Totally fine with 30 days.
Okayish with a reminder every 3 hours (Why quitting? Why not a nice nagging reminder? It’d be much more comfortable to see that the app’s still running…)
Having to look 10+ seconds at the activation screen, which only works with FS as active app: mmh, less so. I guess that’s a bug, isn’t it?

For the wish list: a visible overview of backup patterns, possibility to copy them – I’d take a simple spreadsheet if possible, distinction of file types (for OpenOffice), default patterns.

Well, I hope my comments look as interested as I am.

Grüße aus Schöneberg,

Thomas