Page 1 of 1

That old question about (unnecessary) auto-save

Posted: Wed Jan 23, 2019 7:45 pm
by GarryW
Old topic.

On program exit, or file closure, my Finale very-nearly-always asks whether it should "Save Changes". Even when it "shouldn't". For example, even when the mouse/the keyboard have not been otherwise touched since the file was opened.

I have reviewed previous discussions of the same problem from 2008, 2010, 2012, 2013, and 2017 (!); I didn't see any newer discussions. Fixes from there aren't working. (Did they fix it finally in 25? I don't have it.)

Details below. Maybe the list of what I've tried will save somebody some work.

(I hate the "very-nearly" part of the equation...)

Garry
-------------------------------------------

Finale version: 2014.5 / Windows / 32-bit

Things I have tried:

Not touching the mouse/keyboard in any way since the file was opened (except for the "close".)

"MIDI/Audio / Human Playback" --> "None".

"Edit / Preferences / Human Playback / Allow temporary score adjustments" --> "off"

"Edit / Preferences / Human Playback / Instr. Techniques / Human Playback Preferences Set / Attach to {filename}" --> "off" (or "on".)

"Edit / Preferences / Save / Auto-save file(s) every ___ minutes" --> cleared

"Edit / Preferences / Open / Clean up file data" --> off

"Edit / Preferences / Open / "Automatically convert text in files from other operating systems" --> off

"Edit / Preferences / Edit / Automatic Update Layout" --> off

"Edit / Preferences / Edit / Automatic Music Spacing" --> off

Re: That old question about (unnecessary) auto-save

Posted: Wed Jan 23, 2019 7:53 pm
by motet
I suspect it's hardwired in and was just a quick-and-dirty fix to some problem they were having. Probably the program was not recognizing that the file was changed in some situation and they didn't know how to fix it. Virtually every other computer program in the world that can open and change a file gets this right, so there's no real excuse.

I have a vague recollection that making some change and undoing it set the file to a "not changed" state, but I can't reproduce that so I may have dreamed it.

Re: That old question about (unnecessary) auto-save

Posted: Wed Jan 23, 2019 8:23 pm
by N Grossingink
Years ago, I solved any problems I had with this behavior. When the Save dialog comes up and I truly don't want to save the file, I click "Don't Save". Simple, done. On a Macintosh, there is even a shortcut for this–"Command/D" (Don't save). Is this so goddamn hard?

N.

Re: That old question about (unnecessary) auto-save

Posted: Wed Jan 23, 2019 8:34 pm
by motet
Well, the prompt ("do you want to save?") exists in all programs for a reason. The problem is saving when you don't need to (which destroys the true modification time of the file) and not saving when you should (from the habit of clicking "don't save" because Finale is poorly implemented). I have been burned by both.

Re: That old question about (unnecessary) auto-save

Posted: Thu Jan 24, 2019 12:48 am
by FwL
I don't have this issue with my 2010 version.

I do have it with 25.

Re: That old question about (unnecessary) auto-save

Posted: Thu Jan 24, 2019 12:57 am
by motet
2011 has the problem.