As two others have so eloquently stated ...
"Anything you can do to bring Balsamiq's autosave function
more in line with established conventions will get my vote."
"I dislike auto save/auto correct/auto complete in general .. I have never
been a fan of software adding its own ideas into my work .. I like to be in
full control and do everything manually, including making the decision when to
save, correct my spelling, or close an HTML element. It is great to offer to
those who want it, but I am surprised a user like myself is forced to use it ..
I hope you add a way to disable auto save soon .."
Back in April when I upgraded, I immediately realized this "feature" and inquired about it with similar statements to these in my email to support. The response although kind made me feel like I was the odd-man (ahem, person) out. In almost 30 years of computing I never saw this method of autosave as a popular method. The MS-Office method is the most popular I've seen and would welcome that. Even if revisions are implemented, I would still NOT want my live/production file changed (saved over itself) automatically - only temporary files. Like others, I often make a few changes and need to discard them. The problem with autosave is obvious (and I simply don't see the "problem" without autosave - simply save your work at your own desired intervals - been doing it for decades like at least 1 or 2 others in the computing world ) . The problem with autosave & revisions is that in my scenario, which autosaved backup/revision (or whatever it is called) is the one I want? I have to either watch the clock constantly, or open up each file to see which revision I want to keep as my "real/production" copy. This is a hassle - pure and simple. Revisions? I make them as I need them (I've used the 'save as' feature for decades). The user should have the control - and if a software developer believes they shouldn't that's fine - just provide the option to turn the 'feature" off - so that it's a win-win (the software developer has proven their point but not forced the user into a difficult/ridiculous situation). The night I installed V3 I immediately went back to 2.2.22 and haven't tried V3 again (and will NEVER try any other version unless this autosave thing is removed or optional).
My loss since I would really like to use V3, but this is simply a deal-breaker. No one, no software, no anything should override a developer's/designer's control - especially in programming. Just my 2 cents. Thanks for letting me post. BTW - why does it seem that making this an option is like pulling teeth? Snapshots will be implemented and then a wait and see approach. Is it really that difficult to provide this option? All users win - they can then do whichever they prefer. I guess I'm simply too old and must "get with it"